Rust Was Born From a Broken Elevator — Now It's Replacing C in the Linux Kernel

Key Takeaways

• •Graydon Hoare started Rust in 2006 after a software crash disabled his apartment elevator
• •Mozilla sponsored the project in 2009 — Rust 1.0 shipped in May 2015
• •Linux kernel began accepting Rust code in 2022 — first new language since C in 1972
• •Rust has been the 'most admired language' on Stack Overflow for nearly a decade straight

Timeline

In 2006, Graydon Hoare walked up 21 flights of stairs to his apartment in Vancouver. The elevator was broken again. Its software had crashed.

Hoare was a compiler engineer at Mozilla. He understood exactly what had gone wrong. The elevator's control software was almost certainly written in C or C++, languages that give programmers direct access to memory — and direct access to catastrophic bugs. A dangling pointer, a buffer overflow, a use-after-free error. Any of these could crash an elevator. Or a pacemaker. Or a power grid.

That night, Hoare started writing a new programming language. He called it Rust.

Hoare described Rust as 'technology from the past come to save the future from itself.' He wasn't being poetic — he was being literal.

Hoare described Rust as 'technology from the past come to save the future from itself.' He drew from decades of programming language research — CLU (1975), Erlang (1986), Alef (1992) — languages that explored safer ways to manage memory and concurrency. The key insight was 'ownership': every piece of data has exactly one owner, and when that owner goes out of scope, the data is automatically freed. No garbage collector. No manual memory management. No crashes.

Mozilla saw the potential and officially sponsored Rust in 2009. The language was publicly announced in 2010. Hoare, characteristically modest, stepped down from leading the project in 2013. He'd built the foundation. The community would build the cathedral.

Rust 1.0 shipped on May 15, 2015. Within a year, it topped Stack Overflow's 'most loved language' survey — a position it has held almost continuously ever since. Developers didn't just tolerate Rust; they evangelized it.

The language born from one engineer's elevator frustration is now trusted with the software that controls your car's brakes.

The reason was simple: Rust eliminated entire categories of bugs at compile time. The borrow checker — Rust's signature feature — catches memory errors before your program ever runs. In C, a dangling pointer might crash your software months after deployment, in production, at 3 AM. In Rust, it's a compile error you fix before lunch.

The turning point came in 2022 when the Linux kernel — the most important piece of software in the world, running everything from Android phones to cloud servers to the International Space Station — began accepting Rust code alongside C. Linus Torvalds, creator of Linux and famously resistant to change, approved it. The kernel had been C-only since 1991.

By 2026, Rust has moved far beyond its origins. It's in the Linux kernel. It's in the Windows kernel. It's in game engines, web browsers, databases, and embedded systems. Automotive companies are evaluating it for safety-critical software — the code that controls your brakes and steering.

The irony is profound. Dennis Ritchie created C at Bell Labs in 1972 because programmers needed a language that was close to the hardware but more portable than assembly. C was a masterpiece of pragmatism. It powered Unix, Windows, and the internet. But its manual memory management — the feature that made it fast — also made it dangerous. Microsoft estimated that 70% of their security vulnerabilities came from memory safety bugs in C and C++ code.

Rust doesn't replace C by being different. It replaces C by being C, minus the footguns.

Graydon Hoare rarely gives interviews. He's moved on to other projects. But the language he started in frustration after climbing 21 flights of stairs has become one of the most important developments in software engineering this century.

The root of Rust isn't a grand vision or a corporate strategy. It's a broken elevator and an engineer who decided that software shouldn't crash the things that carry us.

How did this make you feel?

Recommended Gear

Keep Reading

Coding

Rust Was Created Because 70% of All Security Bugs Come from One Type of Error — and C Can't Fix It

5 min read

History

Python Started as a Christmas Holiday Project — Now It Runs the AI Revolution

5 min read

Root Access

The Elevator That Changed Everything: Why the Best Technology Comes From Annoyance, Not Inspiration

6 min read