2 ms·

I'd point out that C only got to this stage of tooling maturity by being around a while -- it's not like less than a year after its first "stable" release it wa

I'd point out that C only got to this stage of tooling maturity by being around a while -- it's not like less than a year after its first "stable" release it was in that state (which is the current age of the Rust stable releases). If Rust manages enough staying power to be here in 20/30/40 years, who knows. Every grizzled and battle-hardened language ecosystem needs to start out young and a bit wild-west-ish before it can gain legitimacy and rock solid tooling.

notalaser 11y ago
Exactly! There's nothing really wrong with Rust -- it's a good language -- but people in this space (and in the embedded world in general, myself included) are skeptical of it simply because reliability is not only something that's inherent to a design, but also something that a) has to be a quality of an implementation, not just of the principles behind it, and b) something that has to be proven in practice, both for the principles and for the implementation. Edit: for what it's worth, I do think it's on the right track on both accounts!