Rust Is Done Being a Cult Favorite. Nearly Half of Companies Now Ship It in Production., GENZ TECH

For most of its life, Rust has been the language developers admired from a distance. It topped Stack Overflow's "most admired language" list for nine straight years, with an admiration rating above 80 percent, while a familiar caveat hung over every conversation: great language, shame about the learning curve, maybe next project. The latest State of Rust survey is the moment that caveat stops holding. The data shows enterprise adoption jumping 10 percentage points in two years, with roughly 45 percent of organizations now making significant use of Rust in production. The language everyone respected but few shipped has quietly become infrastructure.

What the survey actually found

The annual State of Rust survey, run by the Rust project, drew more than 7,000 responses and paints a consistent picture of a language consolidating inside real codebases. Daily usage is at an all-time high. A clear majority of respondents identify as Rust users, up dramatically from where the figure sat in 2018. Around 45 percent of organizations report non-trivial use of Rust in production, a jump of several points from prior years, and roughly a quarter expect their company to hire Rust developers in the next year. These are not the numbers of a hobbyist language. They are the numbers of a technology crossing from early adopters into the mainstream of how serious software gets built.

Why companies are choosing it

The motivations in the survey are revealing because they are not about novelty. Organizations say they reach for Rust to build correct, bug-free software, for performance, and for security and memory safety. That last point is the engine of the whole trend. Rust offers memory safety without a garbage collector, which means it can replace C and C++ in performance-critical systems while eliminating an entire category of the bugs, buffer overflows, use-after-free errors, data races, that have caused a huge share of security vulnerabilities for decades. When governments and large vendors started publicly pushing memory-safe languages as a security priority, Rust went from a nice-to-have to a defensible engineering decision a manager could sign off on. Safety stopped being a developer preference and became a business requirement.

The proof is in who runs it at scale

The adoption numbers would be easy to dismiss as enthusiasm if the production deployments were not so heavy. Cloudflare replaced NGINX across its infrastructure with Pingora, a Rust-based proxy that now serves over a trillion requests a day, and reported 70 percent less CPU usage and 67 percent less memory consumption as a result. The Linux kernel, after years of cautious experimentation, made its verdict plain at its 2025 maintainer summit: the experiment is done, Rust is here to stay. When the most performance-obsessed proxy operator on the internet and the most conservative codebase in computing both commit to a language, the question shifts from whether Rust is ready to why you are not already evaluating it. These are not pilot projects. They are load-bearing systems.

The barriers that remain

None of this means Rust has won, and the survey is honest about the friction. Among developers who do not use it, the most common complaint is still that it is too difficult to learn. Compile times draw consistent criticism, with a meaningful share of users saying slow compilation is a serious problem. And enterprise hesitancy is real: a large fraction of organizations say they have no plans to hire Rust developers, or simply do not know. The learning curve that defined Rust's reputation has not vanished; it has just stopped being a dealbreaker for the teams that have decided the safety and performance payoff is worth the upfront pain. That is a different thing from the curve going away, and anyone planning a migration should budget for it.

Who this affects

For developers, the career math has shifted. A quarter of organizations planning to hire Rust talent in a single year means the skill is moving from resume curiosity to genuine market demand, and the supply of experienced Rust engineers has not caught up. For engineering leaders, the calculus around systems-level rewrites is changing: the memory-safety argument is now backed by enough production evidence that "we use C++ because that is what fast systems are written in" is no longer an unanswerable default. And for the broader software industry, a mainstream memory-safe systems language is simply good news, because it attacks the root cause of a large and persistent class of security holes rather than patching the symptoms after the fact.

Our take

The interesting thing about Rust's tipping point is how undramatic it is. There was no single killer app, no viral moment, just a steady accumulation of production deployments until the adoption curve crossed the line from admired to used. That is exactly how durable technologies win. Hype languages spike and fade; infrastructure languages grind their way in by being the responsible choice for problems that actually matter. Rust spent a decade being the language people wished they could justify. The latest survey is the year the justification arrived, and the honest read is that the learning curve was never the real obstacle. The real obstacle was proof, and the proof is now running a trillion requests a day.

Source: The New Stack, analysis by GenZTech.