Rust Cracks TIOBE Top 10 for First Time as Index Hits 25 Years

Rust has entered the TIOBE top 10 for the first time with a 1.34% rating in July 2026, driven by its memory safety and performance. The index, now 25 years old, still sees Python leading at 18.94% while C and C++ hold strong. This shift signals changing priorities in systems programming and developer hiring.
Rust Cracks TIOBE Top 10 for First Time as Index Hits 25 Years
Written by Lucas Greene

Rust has done what many once thought unlikely. It now sits in the TIOBE Programming Community Index top 10. The July 2026 edition, released on July 5, places the systems language at number 10 with a 1.34 percent rating. That marks its first appearance in the elite group. A year earlier it sat at 18. The jump comes as the index itself turns 25.

Python still dominates. Its 18.94 percent share gives it an eight-point-plus lead over everything else. But even that figure sits well below peaks seen in prior periods. C follows at 10.86 percent, up from the previous year. C++ holds third with 9.12 percent. The gap between those two has widened. Java comes in fourth at 8.03 percent. C# takes fifth. JavaScript, Visual Basic, SQL and R round out the rest of the top 10. TIOBE detailed the full standings.

Paul Jansen, TIOBE CEO, pointed directly to one factor. “Rust’s growing popularity can largely be attributed to its strong focus on memory safety while still generating extremely fast code,” he said in the official release. The language prevents many classes of memory errors at compile time. Developers get C-level speed without the manual allocation headaches that have plagued projects for decades. That combination now carries real weight in production environments.

But. The numbers tell a more measured story. Rust’s 1.34 percent remains modest. It displaced Delphi/Object Pascal, which fell to 11th. Scratch and other niche languages hover just behind. Momentum exists. Whether it sustains depends on adoption beyond enthusiast circles and certain infrastructure teams.

The index’s silver anniversary adds perspective. When it launched in 2001, C, C++ and Java already led. They remain near the top today. Python broke into the top five about a decade ago. C# earned its place roughly 15 years back. Longevity defines this list. Newcomers rarely crack it. Rust now has. That alone sets the July 2026 data apart. TechRepublic covered the milestone and its context in detail.

InfoWorld reported similar findings days after the release. Its piece quoted Jansen on the same memory-safety advantages and noted the exact 1.34 percent figure for Rust. The article also highlighted that TIOBE plans to publish a programming language flowchart to help teams choose tools. Such guidance could influence how companies respond to these shifts. InfoWorld examined the implications for developer hiring and project planning.

Discussions on X reflected immediate interest. One post from TechRepublic noted the jump from 18th to 10th year-over-year and flagged potential reviews of systems programming priorities. Another user highlighted Rust’s preparation through growing libraries and community tools. The conversation stayed factual. No one claimed a wholesale replacement of C or C++. Instead, observers pointed to targeted use in kernels, browsers, cloud services and performance-critical paths.

Memory safety has become a boardroom topic. Major incidents traced to buffer overflows or use-after-free bugs have cost companies millions. Governments now push for memory-safe languages in critical software. Rust answers that call without forcing garbage collection overhead. Its borrow checker enforces rules at compile time. The resulting binaries run fast and predictably. Teams at AWS, Microsoft, Google and others have invested heavily. Those bets appear in the data.

Yet challenges remain. Finding experienced Rust developers still proves difficult, as one 2026 analysis noted. Job postings that specify Rust attract fewer applicants than those listing JavaScript, Python or C++. Larger firms with strong recruiting pipelines manage. Smaller teams face friction. Training helps close the gap over time. So does the language’s reputation for catching errors early, which reduces debugging cycles.

Python’s continued lead reflects its grip on data science, machine learning and automation. Its ecosystem, vast libraries and readability keep it first choice for many new projects. The 18.94 percent rating, while down from prior highs, still dwarfs competitors. C’s rise to second may tie to embedded work and operating system kernels where it remains default. C++ holds strong in games, simulations and high-performance applications. Java powers much of enterprise backend. These four languages have traded places for years. Rust’s entry adds a fifth option with distinct strengths.

SQL’s climb to eighth ahead of R by a slim margin signals steady demand for database skills. That fits broader enterprise needs. JavaScript stays relevant for web work despite its modest 2.72 percent here. Different indices capture web dominance more clearly. TIOBE focuses on search engine results, courses and other signals of broad interest.

Recent coverage builds on these numbers. A Medium piece revisited Rust adoption hurdles four years after an earlier warning. It found hiring remains tough even as the community grows. Another analysis from late 2025 called Rust critical for 2026 precisely because of its safety guarantees and industry backing from the Rust Foundation, whose members include major cloud providers. Those pieces reinforce Jansen’s explanation without contradicting the modest rating.

Look closer at the year-over-year changes. Rust gained 0.33 percentage points. C picked up 1.22. Python dropped more than eight points from the previous July. Such swings happen. They rarely alter the overall order this dramatically. The index measures popularity, not quality or suitability. A language can excel in niche areas yet post low overall numbers. Rust has done exactly that for years. Its top-10 arrival suggests the niche has expanded.

Teams making language choices now face fresh questions. Should new systems code default to Rust where safety matters? Will C and C++ communities accelerate their own safety improvements in response? Microsoft has already introduced Rust components in Windows. The Linux kernel accepts Rust code. Cloudflare and Discord have rewritten performance-sensitive services. These moves accumulate.

Developers who master Rust often report high satisfaction. Surveys have repeatedly named it among the most admired languages. Retention rates sit high. That admiration now pairs with measurable popularity growth. The combination could accelerate further adoption in 2027 and beyond.

The TIOBE chart itself offers no predictions. It simply tracks trends. This month’s headline, however, carries extra weight. A 25-year-old ranking just welcomed a language that did not exist when the index began. Rust first appeared in 2010. Its designer, Graydon Hoare, sought a better tool for systems work. The Mozilla project later embraced it for Servo, its experimental browser engine. From those roots the language matured. The Rust Foundation now stewards it. Corporate support has scaled.

Critics once called it too hard to learn. The borrow checker frustrated newcomers. Error messages have improved. Documentation expanded. Tooling matured. Those barriers have lowered. Universities have begun teaching it. Open-source projects have migrated. The flywheel turns.

Still, no one expects Rust to challenge Python’s lead anytime soon. Its domain differs. Where Python scripts and analyzes, Rust builds the fast, reliable foundations. The two can coexist in the same stack. Many do. A data pipeline might use Python for modeling and Rust for the high-throughput ingestion layer. Such hybrid approaches have grown common.

C++ developers debating a switch now have concrete data. The safety benefits no longer sit in theory. Production systems prove them daily. The performance penalty is negligible or nonexistent in many benchmarks. For new greenfield work, the choice tilts. Brownfield legacy code will stay in its original language for years. Incremental replacement through foreign-function interfaces offers a path.

The broader industry watches. Language popularity influences hiring, training budgets and architecture decisions. A top-10 slot lends credibility in pitch meetings. It reassures risk-averse managers. That psychological shift may matter as much as the raw percentage.

Twenty-five years of TIOBE data show how slowly the top tier changes. Fortran, COBOL and others linger in specialized corners. New languages arrive with fanfare and often fade. Rust has avoided that fate. Its community emphasizes correctness, performance and pragmatism. Those values resonate with engineers who ship critical software.

Future indices will reveal whether this entry becomes a brief visit or the start of a longer stay. For now, the fact stands. Rust has arrived. The numbers back it. Industry conversation has taken notice. Teams that ignore the signal risk falling behind on both safety and talent attraction.

And the timing feels fitting. As the index marks its anniversary, it records a genuine inflection. Older languages adapt. A younger one joins their ranks. The competition benefits everyone who writes code.

Subscribe for Updates

DevNews Newsletter

The DevNews Email Newsletter is essential for software developers, web developers, programmers, and tech decision-makers. Perfect for professionals driving innovation and building the future of tech.

By signing up for our newsletter you agree to receive content related to ientry.com / webpronews.com and our affiliate partners. For additional information refer to our terms of service.

Notice an error?

Help us improve our content by reporting any issues you find.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us