Any ranking of programming languages depends entirely on what it counts. In August 2026 the TIOBE index puts TypeScript nowhere in its top 20, while GitHub reports it as the single most used language on the platform. Neither is wrong. They measure different things, and knowing which is which is the difference between picking a language for a project and picking one because a list said so.
This guide covers the 11 programming languages that matter most in 2026, why each one earns its place, and where the major indices disagree. Two languages entered this edition and two left, which is itself worth understanding before you commit a team to a stack.
How this list was built
The TIOBE index measures search engine results for language names, so it reflects installed base and long-lived codebases. In August 2026 it ranks Python first at 18.53%, followed by C at 11.10%, C++ at 8.62% and Java at 8.25%. It also recorded Rust holding tenth place at 1.45% after entering the top 10 for the first time in July 2026, and MATLAB dropping out of the top 20 for the first time in more than a decade.
The Stack Overflow Developer Survey asks developers what they actually worked with. Its 2025 edition, with 31,771 responses on the language question, puts JavaScript first at 66%, then HTML/CSS at 61.9%, SQL at 58.6%, Python at 57.9% and TypeScript at 43.6%. Python gained seven percentage points from 2024 to 2025, which the survey attributes to AI and data science work.
GitHub's Octoverse 2025 counts contributor activity, and reported TypeScript overtaking Python as the most used language on GitHub, a shift the report attributes to AI-assisted development pushing teams toward typed languages.
The 11 below are the TIOBE top 10 as of August 2026, excluding Visual Basic because its usage is concentrated in legacy Microsoft estates rather than new work, plus TypeScript on the strength of its GitHub position and Go for its role in cloud-native infrastructure. Where a language sits differently across sources, the entry says so.
| Language | TIOBE Aug 2026 | Stack Overflow 2025 | Why it is here |
|---|---|---|---|
| Python | 1st, 18.53% | 4th, 57.9% | Default language of AI and data work |
| C | 2nd, 11.10% | not in top 6 | Embedded, kernels, everything underneath |
| C++ | 3rd, 8.62% | not in top 6 | Performance-critical systems and games |
| Java | 4th, 8.25% | not in top 6 | Enterprise backends at scale |
| C# | 5th, 4.09% | not in top 6 | Microsoft stack and Unity |
| JavaScript | 6th, 2.63% | 1st, 66% | The browser, and everything that followed |
| SQL | 8th, 1.88% | 3rd, 58.6% | Every analytical question ends here |
| R | 9th, 1.56% | not in top 6 | Statistics and research computing |
| Rust | 10th, 1.45% | not in top 6 | Memory safety without a garbage collector |
| TypeScript | not in top 20 | 5th, 43.6% | 1st on GitHub per Octoverse 2025 |
| Go | 14th, 1.07% | not in top 6 | Cloud-native services and tooling |
The 11 languages
Python. First on TIOBE at 18.53% and the widest lead in the index. It became the default for machine learning, data pipelines and scripting because the libraries arrived there first and stayed. Our guide to Python for data analysis covers the path from a notebook to a deployed API, and why Python fits AI work goes into the ecosystem in more detail. The trade-off is runtime speed, which is why performance-sensitive parts get pushed into C or Rust extensions.
TypeScript. The most consequential change in this edition. GitHub's Octoverse 2025 reported it as the most used language on the platform, ahead of Python, and attributed the shift to AI-assisted development: when a model writes code you did not, a type system is what catches the mistake. It does not appear in TIOBE's top 20 at all, because TIOBE counts search volume for the language name and TypeScript queries often resolve as JavaScript. For anyone building web applications today it is closer to a default than an option, as our guide to modern frontend development shows in practice.
JavaScript. First in the Stack Overflow survey at 66%, sixth on TIOBE at 2.63%. The gap between those two positions is the clearest illustration of methodology mattering: JavaScript is used by two thirds of developers and searched for comparatively little, because the questions people ask are about frameworks rather than the language.
C. Second on TIOBE at 11.10%, and the reason is structural. Operating system kernels, embedded firmware, database engines and the runtimes of most other languages on this list are written in it. Nothing about C is fashionable, and nothing replaces it either.
C++. Third at 8.62%. Where deterministic performance and direct memory control are requirements, C++ remains the standard: game engines, trading systems, simulation, browser internals. It carries decades of accumulated complexity, which is exactly the opening Rust is pushing into.
Java. Fourth at 8.25%, and closing on C++ in recent TIOBE readings. Java runs a large share of enterprise backends, Android applications and big data tooling. Modern releases have narrowed the verbosity gap that drove teams away a decade ago.
C#. Fifth at 4.09%. Strongest inside the Microsoft ecosystem, and the language of Unity, which makes it the practical entry point for a large part of game development.
SQL. Eighth on TIOBE at 1.88% and third in the Stack Overflow survey at 58.6%, used by more developers than Python. It is the one language on this list almost nobody chooses and almost everybody writes, because every analytical question eventually becomes a query.
R. Ninth on TIOBE at 1.56%. Concentrated in statistics, biostatistics and academic research, where its modelling and visualisation packages still have no direct equivalent. Python has taken most of the general data science ground, which our overview of data science covers in context.
Rust. Tenth at 1.45%, having entered the TIOBE top 10 for the first time in July 2026. It offers memory safety without a garbage collector, which is why it is appearing in kernels, browser engines and infrastructure written previously in C or C++. Its position is narrow: Delphi/Object Pascal sits at eleventh with 1.37%, so the top-10 slot is contested.
Go. Fourteenth at 1.07%, and included here on relevance rather than ranking. Kubernetes, Docker, Terraform and a large share of cloud-native tooling are written in Go, which makes it hard to work in modern infrastructure without reading it. Our guide to Docker and Kubernetes for data engineering covers that layer.
What changed from the 2025 edition
PHP and Swift are out of this list. PHP sits at thirteenth on TIOBE with 1.11% and still runs an enormous installed base of web applications, so its absence reflects the eleven-slot limit rather than a judgement about the language. Swift is at seventeenth with 0.96%, and its relevance is concentrated in Apple platform development, which makes it essential for that work and narrow outside it.
TypeScript and Rust are in, for the reasons above. Both entries mark the same underlying shift: type safety and memory safety are being treated as requirements rather than preferences, and AI-generated code has accelerated that.
Worth noting what is not here. MATLAB left the TIOBE top 20 in August 2026 after more than ten years inside it. Kotlin does not appear in the TIOBE top 20 for August 2026 and did not surface in the top usage tiers of the sources consulted, so it is not included despite its position in Android development.
How to actually choose one
Rankings tell you what exists and what has support. They do not tell you what your project needs, and treating them as a decision framework is how teams end up rewriting a service in a language nobody on staff can maintain.
Three questions matter more than any index. The first is what the problem requires, in performance, safety and ecosystem terms. The second is what the team can already maintain, including a year from now when whoever chose it has moved on. And the third is what the surrounding stack expects, since a language that fights your infrastructure costs more than it saves. A team building data pipelines on Kubernetes has a different answer from one shipping an iOS app, and both answers can be correct.
The languages on this list are all safe in the sense that matters: each has an active ecosystem, hiring pool and long-term support. The risk in a language decision rarely comes from the language.
On the one most used in data work, read the advantages and disadvantages of Python.
In the Android world, the duel is in Java versus Kotlin.
If your company is choosing a stack for a new product, or weighing whether an existing codebase justifies a migration, our specialists can help you assess the trade-offs against your team and infrastructure. Talk to our team and move your data maturity forward. ⬇️
What is the most popular programming language in 2026?
It depends on what is measured. The TIOBE index for August 2026 ranks Python first at 18.53%, based on search engine results. The Stack Overflow 2025 survey ranks JavaScript first at 66% of developers. GitHub's Octoverse 2025 reports TypeScript as the most used language on the platform. All three are accurate for their own methodology.
Should I learn Rust or TypeScript in 2026?
They solve different problems, so the answer follows the work. TypeScript is the practical default for web and application development, and GitHub reports it as the most used language on the platform. Rust fits systems programming where memory safety matters without a garbage collector, and it entered the TIOBE top 10 in July 2026.
Why is TypeScript missing from the TIOBE index top 20?
Because TIOBE counts search engine results for language names, and TypeScript questions frequently resolve as JavaScript queries. The index measures search visibility rather than developer usage, which is why a language can lead on GitHub contributor activity while sitting outside TIOBE's top 20 entirely.
Is C still relevant in 2026?
Yes, and structurally so. C ranks second on TIOBE at 11.10%. Operating system kernels, embedded firmware, database engines and the runtimes of most higher-level languages are written in it. Its relevance comes from what depends on it rather than from new projects choosing it.
Which programming language should my company choose for a new project?
Start from the requirement, not the ranking. Assess what the problem needs in performance, safety and ecosystem terms; what your team can maintain a year from now; and what your existing infrastructure expects. Every language on this list has an active ecosystem and hiring pool, so the risk usually sits in the fit rather than the language.
