Five years of steady growth
In 2020 Rust is voted “most loved language” in the annual Stack Overflow developer survey for the fifth consecutive year. The figure does not measure absolute adoption — Rust remains a niche language compared to Python or JavaScript — but it indicates that those who use it do not want to go back. The satisfaction reflects the language’s guarantees: compile-time memory safety, absence of data races, native performance, all without a garbage collector.
Since version 1.0 released in 2015, the ecosystem has consolidated. Cargo, the package manager and build system, has become the reference point for dependency management. The crates.io registry exceeds forty thousand libraries. Stable async/await, introduced in version 1.39 in November 2019, has opened Rust to asynchronous programming with ergonomics comparable to higher-level languages.
Microsoft and memory safety
Microsoft publicly announces that approximately 70% of security vulnerabilities in its products are caused by memory management errors in C and C++ code. The statistic, consistent with Google’s data for Chromium and Android, makes explicit a problem the industry has known about for decades but has not yet solved at scale.
Microsoft begins experimenting with Rust for Windows components and system tools. The Rust/WinRT project explores bindings to Windows APIs. This is not about rewriting Windows in Rust, but about evaluating the language for new components where memory safety is critical.
Amazon and Firecracker
Amazon Web Services uses Rust for Firecracker, the lightweight virtual machine monitor that powers AWS Lambda and Fargate. Firecracker must be fast, secure and present a minimal attack surface — requirements that align directly with Rust’s guarantees. AWS’s choice validates the language for high-responsibility infrastructure software.
The path to the Linux kernel
In 2020 the proposal to introduce Rust as a second language in the Linux kernel takes concrete shape. Nick Desaulniers and other developers present experimental patches and technical documents exploring how to integrate Rust’s ownership model with the conventions of a kernel written in C. The main obstacles are interoperability with existing C code, kernel allocator management and hardware architecture support.
The proposal is not unanimously welcomed: part of the kernel community expresses scepticism about the added complexity. But the support of influential developers and the evidence of memory safety benefits keep the debate active.
A language finding its place
Rust does not replace C or C++ in existing projects. Its space lies in new components where memory safety is a requirement, not an optional: cloud infrastructure, system tools, drivers, firmware. Adoption by Microsoft, Amazon and the discussion in the Linux kernel mark the transition from a promising language to an industrial tool.
Link: rust-lang.org