Explainer graphic: what Rust is good at, who runs it, and four steps to write a first program
Rust in one picture: the memory-safety numbers, where it already runs, and how a beginner starts.

Rust keeps turning up in odd places. It is inside the Linux kernel, inside Android, inside the servers that run Amazon's cloud, and in government advice about how software should be built. Here is what the fuss is actually about.

The short answer: Rust is a programming language built to be as fast as C and C++ without their most dangerous class of bugs: memory errors. Operating-system makers, cloud providers and security agencies have decided those bugs are worth engineering away, and Rust is the main tool they reach for. It is harder to learn than Python and slower to compile, but mainstream in 2026.

What Rust is good at

Most software is written in languages that either manage memory for you at run time (Java, Python, JavaScript) or leave it entirely to the programmer (C, C++). The first group is safe but carries a runtime cost. The second is fast but easy to get wrong, and getting it wrong is how a lot of serious security holes start.

Rust's trick is a compile-time rule set called ownership. The compiler checks who may touch each piece of memory, and when, before the program ever runs. The official site puts it plainly: no runtime, no garbage collector, and a type system that guarantees memory safety and thread safety.

That matters because memory bugs are not rare. In July 2019, Microsoft's security response centre reported that around 70% of the vulnerabilities it assigned a CVE each year were memory-safety issues. Google's Android team reported a similar picture in September 2024: memory-safety bugs were 76% of Android vulnerabilities in 2019 and 24% in 2024, after new code moved to safer languages.

Who actually runs Rust in 2026

The 2018 version of this post listed a handful of small consultancies. The list looks rather different now.

Where Rust is already in production, with the source for each claim
PlaceWhat runs in RustSource
Linux kernelInitial Rust support landed in Linux 6.1 in December 2022; mainline drivers now include Android Binder, the Nova and Tyr GPU drivers and a null block driverKernel Newbies, Rust for Linux
AndroidNew code steered to memory-safe languages; memory-safety share of bugs fell from 76% to 24% between 2019 and 2024Google Security Blog
AWS cloudFirecracker (behind Lambda), Bottlerocket, and parts of S3, EC2 Nitro and CloudFront, per a February 2022 AWS postAWS Open Source Blog
Windows and MicrosoftMicrosoft is a founding member of the Rust Foundation and publishes its own Rust-on-Windows developer guideMicrosoft Learn
Rust FoundationPlatinum members include Arm, AWS, Google, Huawei, Meta, Microsoft, NVIDIA and OpenAIRust Foundation

The Android numbers are the ones to remember. Those monthly security patches your phone gets are, to a large extent, memory-bug fixes, which is why how long a phone keeps getting updates matters so much.

Why governments care

Security agencies have moved from suggesting memory-safe languages to naming the alternative as a bad practice. CISA's Product Security Bad Practices guide, version 2.0 from January 2025, lists building new product lines in a memory-unsafe language such as C or C++ as its first bad practice. It also asked manufacturers to publish a memory-safety roadmap by the end of 2025.

In June 2025, CISA and the NSA followed with a joint guide, Memory Safe Languages: Reducing Vulnerabilities in Modern Software Development, aimed at industry, government and universities. The guidance is voluntary. It is still a clear signal about where big buyers of software want the industry to go.

How a beginner starts

You do not need a computer-science degree, just a terminal and some patience. The current stable release is Rust 1.99.1, and the language ships a new version roughly every six weeks; 1.99.0 arrived on 1 October 2026.

  1. Install with rustup. The Get started page gives one command for macOS, Linux and WSL, and a small installer for Windows. Windows may ask for the Visual Studio C++ build tools.
  2. Check Cargo. Run cargo --version. Cargo is Rust's build tool and package manager, and it comes with the install.
  3. Make a project. cargo new hello-rust creates a folder with a ready-made Hello World; cargo run builds and runs it.
  4. Read the Book. The Rust Programming Language is free online and installs offline with rustup doc --book. Start with the guessing-game chapter, then ownership.
  5. Expect the compiler to argue. Early on it rejects a lot of code. Its error messages are unusually good, so read them; that is the learning curve, not a bug.

The trade-offs

Rust is not free. The 2025 State of Rust Survey, answered by 7,156 people, named slow compile times and storage use as the biggest headache, with a steady worry that the language is becoming more complex.

Debugging is the other sore spot. In the Rust Debugging Survey published in September 2026, about 74% of more than 2,300 respondents struggled with how debuggers display values, and most people simply used print statements instead.

Then there is scale. Stack Overflow's 2025 Developer Survey found 14.8% of respondents had done extensive work in Rust in the past year. That is a solid minority, not a majority. For a quick first job, Python is still the safer bet; Rust wins for systems, infrastructure and anything security-sensitive.

Frequently asked questions

Is Rust replacing C and C++?

Not wholesale. Most of Android and Linux is still C. The pattern in every source above is the same: new code goes to Rust, old code is left alone or migrated slowly where the risk justifies it.

Should a complete beginner learn Rust first?

It is doable, and the Book is written for newcomers, but you will meet ownership and borrowing in week one. Many people find it easier after a gentler language. If you already know a little programming and care about how computers really work, Rust is a rewarding second language.

If you want to see what the fuss is about, spend one evening on it: install rustup, run cargo new, break something, and read the error. That single loop explains Rust better than any overview, including this one.