DBdbrgn·Nov 30, 2018
Probably because of snippets like this one:
"the idea of putting "Embedded" on the front page and trying to advertise Rust as a useful embedded language isn't just laughable--it's dangerous. Rust is so far from useful in embedded that people who try to use it will NEVER come back"
Embedded is still at its early development stages, just like WASM and just like asynchronous network programming. Still, all those are on the front page.
WASM a year ago and wasm todays is a tremendous difference. A year ago, in my opinion, WASM was something for experimentation. Now, a lot of the ecosystem "just works" and is developing really quickly. You can write a working JS library and upload it to NPM without even touching a line of JavaScript code.
Async (network) programming in Rust with async/await is promising but still in flux, so the ecosystem hasn'
Read the rest
t settled yet. Still, a lot of systems already use it in production.
Embedded in Rust a year ago was mostly a list of blogposts, an early draft of HAL traits and some random register binding crates. You had to use nightly, and your code would frequently break. But in just a few weeks, you'll be able to use Embedded on stable, there is an active ecosystem developing around svd2rust, groups like stm-rs and lpc-rs are forming and a lot of device agnostic drivers have already been written. Combine that with a very promising preview of a new version of the RTFM framework. It's not production ready yet, but I'd estimate it will be within 2 years. See https://github.com/rust-embedded/awesome-embedded-rust for a summary of the ecosystem.
The problem with the post above is not that it's written in a strong tone. It's that it's uninformed, generalizing and unfair.