> Rust isn't viable for embedded platforms, at least not yet. no_std allows the important hooks of panicking, output and allocation to be implemented by the us

> Rust isn't viable for embedded platforms, at least not yet. no_std allows the important hooks of panicking, output and allocation to be implemented by the user. It's also very easy to put in hard-coded pointers that represent memory-mapped hardware. And there's no GC. Furthermore, it's entirely possible to convert only a portion of a project to using Rust while working to gradually to replace/reimplement. > If I were to make one change to C, it would be to completely rip out the #include system [preprocessor] and bring a proper modules system. Congratulations, you've just reinvented Java, D, Rust and Go. > Apart from that, it's pretty much perfect. This seems like a religious opinion rather than having understanding of different paradigms. Have you been paying attention to why Java, Erlang, Go, Rust and exist? Rust has numerous advantages over C that eliminate entire categories of problems without sacrificing speed. If you can't see that, then maybe you don't want to see it.