Ten editions in. That’s not nothing. The 2025 State of Rust Survey results dropped last week, and for what it’s worth, the headline isn’t dramatic: responses dropped slightly (around 7,100 this year versus 9,400 last year), most answers matched last year within a percentage point, and the community looks… stable.
And honestly? That’s a good sign.
Stability Is Maturity
When a language is young and scrappy, survey results swing wildly year to year. Pain points get fixed, new ones appear, adoption explodes in some sector, tooling catches up. You get noise. The fact that Rust’s survey results are now basically flat year-over-year tells me the ecosystem has settled into something people can actually rely on.
This fits my own experience. I’ve been using Rust for tooling and some systems-adjacent work for a few years now, and it stopped feeling experimental a while back. The borrow checker is something I think with now, not against. That shift happened quietly.
The Response Drop Is Worth Thinking About
The survey team flagged something worth noting: in 2025, the Rust project published multiple surveys — one on Compiler Performance, one on Variadic Generics. Survey fatigue is real, and people have limited time. If you’re asking your community to weigh in on multiple targeted surveys throughout the year, it makes sense that fewer people sit down for the longer annual one.
This is actually a healthy sign of the project maturing. Asking focused questions about specific problems (compiler performance, language features) means the team knows enough about what to investigate. Early-stage projects don’t have that luxury.
The Stable Compiler Trust Signal
One thing the survey confirms: people overwhelmingly develop on stable Rust and keep up with releases. That’s a quiet endorsement of how the release process has been run. Rust ships every six weeks, the stability guarantees hold, and users trust it enough that they don’t feel pressure to chase nightly for features. For a systems language with the complexity Rust has, that’s genuinely hard to pull off.
Compare that to ecosystems where you’re constantly hedging against breaking changes — it’s a different relationship with your tools.
What I’d Want to See Next
The team mentioned they’re thinking about how to combine the State of Rust survey with the ongoing Rust Vision Doc work. That interests me. A survey that’s tied to actual roadmap decision-making is more useful than one that’s purely descriptive. The gap between “here’s what people said” and “here’s how it changed what we built” is where surveys either earn their keep or become noise.
If you haven’t read through the full report, it’s worth a skim even if you’re not deep in the Rust community. Survey methodology aside, it’s a reasonable cross-section of where a mid-size systems language sits after a decade of serious development.
Ten years of this survey. The fact that it’s a little boring now is the point.