3 ms·
Write from scratch, maybe. Rewrite, I don't think it will happen anytime soon. In fact, the more time it passes, the more code needs to be rewritten. Regarding
by scoutt 8y ago
Write from scratch, maybe. Rewrite, I don't think it will happen anytime soon. In fact, the more time it passes, the more code needs to be rewritten.
Regarding firmware, if the talk was about bare-metal embedded development, then I think Rust is the solution to a problem that no one has.
Since the food on my table comes from firmware development, I passed several days trying to understand the reasons to move to the approach described here: http://blog.japaric.io/brave-new-io/ http://blog.japaric.io/brave-new-io/ (Embedded in Rust blog, great reading BTW).
But found little. It's a nice toy but it may be too much.
If that is the trend, then I think Rust for Embedded is the answer to a question no one asked, because in my work, if I need to set a bit into a register, I have to be sure it's fking set; not playing around "just because it may be problematic".
- blub 8y agoI hope this idea of taking the complexity of memory management and encoding it in the language syntax is an evolutionary dead end, because that Rust code looks genuinely painful. Otherwise I agree that a rewrite is nonsense. In these kinds of huge projects, only a gradual solution that can co-exist with the existing code base could work, if anything. An example would be tightening the safety of the existing code through static analysis of the kind offered by Frama-C.
- pjmlp 8y agoThe problem with static analysis of the kind offered by Frama-C, is that many developers not even at gunpoint bother to use them.