# Rust: A broken elevator and a gate for memory safety

> What connects a broken elevator to Rust? Graydon Hoare’s account, ownership checks before execution, and Rust’s use in Android system code.

*2026-11-03T17:35:27Z*

What does a broken elevator have to do with a programming language?

In 2006, Graydon Hoare was frustrated with his building’s broken elevator, as he later recalled. The story opens a larger question: how can we build software close to the hardware without leaving invalid memory use waiting to surface at runtime?

## In 60 seconds

Rust began as Hoare’s personal project in 2006; Mozilla later supported it. Stable version 1.0 arrived in May 2015. Ownership is a central idea: compiler-checked rules prevent invalid uses of memory. Today, Rust is used in Android operating-system code itself.

## The elevator, in its creator’s account

In his 2025 Rust Foundation article, Hoare revisited his frustration with the broken elevator in 2006. His rust-prehistory archive identifies 2006–2009 as the personal-project phase, followed by a private Mozilla project from late 2009.

The elevator account is not a technical diagnosis. It does not establish a particular memory bug, identify the code as C++, or show that Rust was written to repair that elevator. We keep the story attributed to the person who told it.

## From personal project to stable language

Mozilla’s support helped the project grow, with Servo becoming a place to exercise and develop the language. Servo is a browser engine; that does not mean all of Firefox is written in Rust.

The official Rust 1.0 announcement on 15 May 2015 connects efficient systems software, resource control, and safety guarantees. The 2006 personal beginning and the 2015 first stable release are different milestones.

## The doorman says the apartment was handed back

With C++, we saw speed. Can we retain resource control while protecting memory too? Rust checks ownership rules before execution. The official Book demonstrates moving a String from one variable to another. Trying to use the old variable after that move is rejected by the compiler.

Like a doorman saying: that apartment’s been handed back. Who are you visiting?

That is our analogy. The example does not first execute a use-after-free; compilation prevents the invalid use from reaching execution. Nor does it eliminate every kind of bug. Safe Rust also relies on unsafe code and external boundaries fulfilling their safety contracts.

## Rust inside Android itself

AOSP documentation identifies Android 12 as introducing Rust for platform development, bringing memory and thread safety with performance similar to C and C++.

This concerns parts of the operating system. It does not mean all of Android has been rewritten in Rust, or that every application should replace Kotlin or Java with it. Rust ranked tenth in the October 2026 TIOBE index, a search-based popularity indicator rather than a performance or security test.

## Learn it if

Learn it to build systems, servers, and fast tools with memory safety. Start by understanding who owns a value, who borrows it, and how long that borrow remains valid. A compiler rejection becomes a chance to understand the rule before an error reaches a running program.

## Frequently asked questions

### Was the elevator failure caused by a memory bug?

The origin account does not establish a technical diagnosis. We attribute the broken-elevator story to Hoare without inventing its cause.

### Does Rust prevent every bug?

No. Ownership rules prevent classes of memory errors. Logic bugs remain possible, and unsafe code and external boundaries must uphold safety contracts.

### Is all of Android written in Rust?

No. Rust is used in parts of Android platform code. That is different from saying the entire system or all its apps are written in Rust.

## Sources

- [Graydon Hoare — 10 Years of Stable Rust, 2025](https://rustfoundation.org/media/10-years-of-stable-rust-an-infrastructure-story/)
- [Graydon Hoare — Rust prehistory](https://github.com/graydon/rust-prehistory)
- [Rust Core Team — Announcing Rust 1.0, 2015](https://blog.rust-lang.org/2015/05/15/Rust-1.0/)
- [Mozilla — Servo collaboration, 2013](https://blog.mozilla.org/en/mozilla/mozilla-and-samsung-collaborate-on-next-generation-web-browser-engine/)
- [The Rust Book — ownership](https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html)
- [Rust — unsafe contracts](https://rust.docs.kernel.org/next/core/keyword.unsafe.html)
- [AOSP — memory safety](https://source.android.com/docs/security/test/memory-safety)
- [Android — Rust in the platform, 2021](https://security.googleblog.com/2021/04/rust-in-android-platform.html)
- [TIOBE Index — October 2026 edition checked 3 November](https://www.tiobe.com/tiobe-index/)

## Read next

- [Python](https://fadymondy.com/en/blog/why-slow-python-won-ai)
- [JavaScript](https://fadymondy.com/en/blog/javascript-history-why-it-won)
- [Java](https://fadymondy.com/en/blog/java-history-cable-box-deal-android)
- [C++](https://fadymondy.com/en/blog/cpp-history-from-phd-to-arduino)

---

Source: https://fadymondy.com/en/blog/rust-history-from-broken-elevator-to-memory-safety
