By Two months ago, TIOBE analyst Paul Jansen called the plateau. Rust had spent a full year going nowhere in the rankings — bouncing between #13 and #16 — and Jansen wrote that the language might finally be leveling off. The June 2026 TIOBE Index just made him revise that assessment. Rust jumped to #12, its all-time highest position ever, and Jansen now says a top-10 breakthrough looks more plausible than it did earlier this spring.
What the Numbers Actually Say
The June 2026 TIOBE Index has Python holding #1 at 18.96% (down from 19.98% in May), C at #2 with 10.77%, and C++ moving back ahead of Java at #3. Rust sits at #12 — a four-position jump in just two months after a full year of stagnation. For context, ByteIota covered Rust’s drop to #16 in April, when Jansen was writing post-mortems on the hype cycle. Now he’s walking that back.
This matters beyond the number itself. TIOBE tracks search engine signals — tutorials, job postings, course demand, vendor documentation. A jump of this size in two months means something concrete happened in the world to drive Rust searches upward. Three things did.
Three Catalysts Behind the Jump
The Linux Kernel Just Mandated Rust
DRM subsystem maintainer Dave Airlie announced that new DRM (Direct Rendering Manager) drivers must be written in Rust, with C disallowed for new contributions within approximately one year. That makes the DRM subsystem the first major kernel subsystem to mandate a language other than C in Linux history. Linux 7.1 is already shipping with a GPU buddy allocator in Rust, a DMA coherent API rework, shared memory GEM helpers, and the NVIDIA Nova driver — all Rust. When the Linux kernel starts making language mandates, the wider industry takes notice, and that notice shows up in search volumes.
Government Memory-Safety Deadlines Are Real Now
CISA’s January 2026 deadline for organizations to publish memory-safety roadmaps was not aspirational — it was a concrete requirement. Combined with prior guidance from the White House, NSA, and international cybersecurity authorities pointing away from C and C++ for critical infrastructure, corporate Rust adoption accelerated through the first half of 2026 to meet these requirements. This is not developer enthusiasm. It is procurement and compliance driving adoption, which is how enterprise technologies actually cross the chasm.
Rust Became the Invisible Engine of the Python Ecosystem
uv — the Python package manager written in Rust and acquired by OpenAI through the Astral deal in March 2026 — now sees over 126 million downloads per month. Ruff, also Rust-written, serves hundreds of millions of downloads monthly and runs 1,000x faster than traditional Python linters. The developers using these tools are Python developers, not Rust developers. Most of them never think about the language underlying their toolchain. But every install, every search for “how to use uv,” every Stack Overflow question about ruff — those are TIOBE signals attributed to Rust’s ecosystem reach.
The Admiration Rate Dip Is Actually Bullish
Stack Overflow’s 2025 survey showed Rust’s “most admired” rate dropped from 83% to 72%, and some took that as a sign of cooling enthusiasm. It’s not. When a language transitions from enthusiast-driven to institutionally mandated, the percentage of people who actively chose it declines. More developers are now being asked to write Rust because their employer requires it, not because they fell in love with the borrow checker at a conference. The same pattern appeared when JavaScript went corporate and when Python became the mandatory data science tool. The admiration rate for Python is now 52%. Nobody is writing Python obituaries. The drop from 83% to 72% is Rust going mainstream, not Rust going stale.
What Top 10 Actually Requires
The languages sitting between Rust and the top 10 at positions 7–11 are approximately Go, Kotlin, PHP, Swift, and TypeScript. TypeScript is not going anywhere — the web and agent-building ecosystem is too entrenched. PHP has been on death watch for fifteen years and keeps not dying. Swift remains siloed in Apple platforms. Go and Rust are the most interesting comparison: Go sits higher on TIOBE largely because it has been around longer, has more web content, and powers a huge share of cloud infrastructure. But Rust is closing the gap in systems programming specifically, and Go does not have a kernel mandate or a government compliance tailwind.
RedMonk, which uses GitHub and Stack Overflow data rather than general search signals, already ranks Rust at #7–8. The gap between TIOBE’s #12 and RedMonk’s #7-8 suggests TIOBE is lagging developer reality, not leading it. As Rust documentation, courses, and tutorials accumulate online, the TIOBE signal will continue to catch up. A consistent top-10 appearance by 2027 is now a reasonable expectation rather than an optimistic one.
Should You Invest in Rust in 2026?
If you are building systems software, embedded code, high-performance networking, or GPU drivers — yes, without hesitation. The kernel mandate, the government compliance requirement, and the production deployments at AWS, Cloudflare, Google, and Microsoft have established Rust as the default choice for new systems work. If you are a Python or JavaScript developer, you are likely already using Rust without knowing it. The ecosystem investment is happening whether you participate directly or not. The borrow checker is famously hard. But the question is no longer whether Rust is worth learning — it is whether you can afford to be the developer who never encountered it.
