Good state-of-the-language piece: compile times, borrow checking, async, ecosystem maturity.

The Rust project published a reality check. This is not a “Rust is doomed” post, and it’s not a victory lap either. More like: we talked to a bunch of people, and yes, the problems you already think Rust has are in fact the problems people keep running into.

The interesting part is the shape of those problems. Compile times are still a thing, but they’re not really hard blockers for most people. The borrow checker is still brutal for beginners, but it bothers experts a lot less, which tells you some of that pain is onboarding pain, not necessarily evidence the language is broken. Async is still messy in the way Rust async has been messy for a while, except here they are pretty explicit that there are actual next steps they think can help.

Then you get to the ecosystem story, which is maybe the most important one. A healthy crate ecosystem is one of Rust’s strengths, but people still do not always know which crates to trust, which ones are effectively standard, or whether the thing they need exists yet in their domain. In worlds like embedded, GUI, and safety-critical work, that maturity gap gets a lot more obvious.

I applaud this post and the intent behind. I use Rust daily. I’ve felt this pain. Sure Rust can be improved. But this shows the project is listening and it shows they have clear plans to smooth out areas where there’s friction.