8 min read1 hour ago

–

In August 2025, something historic happened in the world of software development.

Press enter or click to view image in full size

Photo by Brecht Corbeel on Unsplash

For the first time in over a decade, the programming language rankings on GitHub experienced a seismic shift:

TypeScript overtook both Python and JavaScript to become the most-used language on the platform.

This isn’t just a numbers story. It’s a signal that the entire software development landscape is being reshaped by AI — and TypeScript has become the default language for the AI-assisted era.

The Numbers Tell a Remarkable Story

According to GitHub’s Octoverse 2025 report, TypeScript finished August with 2,636,006 monthly contributors — roughly 42,000 more than Python. But the growth trajectory is even more striking:

TypeScript added over 1 million new contributors in 2025 alone, representing a staggering 66% year-over-year increase.

To put this in perspective:

• Python added 850,000 contributors (+48% YoY)
• JavaScript grew by 427,000 contributors (+25% YoY)

Both impressive in isolation, but TypeScript’s momentum is undeniable.

This marks the most significant language shift GitHub has seen since they started tracking these metrics more than a decade ago.

Press enter or click to view image in full size

Photo by Timothy Cuenat on Unsplash

Why Now? The AI Connection

The timing isn’t coincidental. The explosion in TypeScript adoption directly correlates with the rise of AI-assisted coding tools like GitHub Copilot, Cursor, and others.

Here’s the critical insight that most coverage is missing: AI coding assistants desperately need type systems to work reliably.

The 94% Problem

A 2025 academic study found that 94% of LLM-generated compilation errors are type-check failures.

Think about that for a moment. When GitHub Copilot, Cursor, or any other AI assistant generates code, the vast majority of its mistakes are type-related — variables of the wrong type, functions called with incorrect arguments, objects missing required properties.

TypeScript catches these errors immediately, before you ever run the code. In a JavaScript codebase, these bugs slip through to runtime, causing production failures. In TypeScript, they’re red squiggly lines in your editor.

Press enter or click to view image in full size

Photo by Boitumelo on Unsplash

What TypeScript’s Creator Says About AI

Anders Hejlsberg, TypeScript’s creator (and the same mind behind C# and Turbo Pascal), explained it perfectly in a recent interview with GitHub:

“AI’s ability to write code in a language is proportional to how much of that language it’s seen. AI has seen tons of JavaScript, Python, and TypeScript so it’s great at writing them.”

But there’s more to it than just familiarity. Hejlsberg continued:

“If you ask AI to translate half a million lines of code, it might hallucinate. But if you ask it to generate a program that does that translation deterministically, you get a reliable result. That’s the kind of problem types were made for.”

In other words: In a world where code is written by both humans and machines, types aren’t bureaucracy. They’re truth checkers.

The Framework Effect: When Defaults Become Destiny

Nearly every major frontend framework now scaffolds projects with TypeScript by default. When you run create-next-app, npm create astro@latest, or spin up a new SvelteKit project, you get TypeScript out of the box.

When the most widely-used frameworks in the world all default to TypeScript, and when AI assistants generate code that TypeScript catches errors in more reliably, and when the setup has become painless — the outcome becomes inevitable.

The tooling ecosystem has reached a tipping point. Tools like Vite, ts-node, Bun, and modern IDE configurations hide the boilerplate setup that once made TypeScript feel heavyweight.

Now, starting a TypeScript project is as simple as starting a JavaScript one — except you get safety, better autocomplete, and fewer 3 a.m. debugging sessions.

The Global Developer Boom

The TypeScript surge is happening against the backdrop of explosive growth in the developer community overall.

In 2025, more than one new developer joined GitHub every second on average — 36 million new developers in a single year.

And here’s the kicker: 80% of new developers on GitHub use GitHub Copilot within their first week. AI-assisted coding isn’t something developers “grow into” anymore. It’s part of the default experience from day one.

Press enter or click to view image in full size

Photo by Mohammad Rahmani on Unsplash

This means millions of developers are learning to code in an environment where:

• ✨ AI suggests most of their code
• 🛡️ Type systems catch AI mistakes
• 🚀 Modern frameworks default to TypeScript

For these developers, TypeScript isn’t a “step up” from JavaScript — it’s just how you write JavaScript in 2025.

What About Python and JavaScript?

Let’s be clear: Python isn’t going anywhere. It remains completely dominant in AI, machine learning, and data science.

In AI-tagged repositories, Python accounts for nearly half of all projects:

• 582,196 repositories (+50.7% YoY)
• Jupyter Notebook usage grew 17.8% YoY within AI projects

The New Programming Language Landscape

The difference is specialization:

Python → Model training, data pipelines, ML infrastructure

TypeScript → Application development, web APIs, dashboards, frontend stack

JavaScript → Still massive (2.15M contributors) but growth slowing

In the past 12 months, developers created 5.4 million new TypeScript repositories — a 78% increase year-over-year. That’s not just framework churn or toy projects. These are real codebases where teams are betting their products on TypeScript.

TypeScript Had to Stop Being Written in TypeScript

Here’s a fascinating technical detail that rarely gets discussed: TypeScript itself had to stop being written in TypeScript.

When the language launched in 2012, it was famously self-hosted — the TypeScript compiler was written in TypeScript itself. This kept it portable and hackable, but eventually performance became a bottleneck.

As Hejlsberg revealed in his GitHub interview:

“As much as it pained us to give up on self-hosting, we knew we couldn’t squeeze any more performance out of it. We experimented with C#, with others, and finally chose Go. The performance gain was 10X. Half from being native, half from shared-memory concurrency. You can’t ignore 10X.”

The new compiler is a “carbon copy” of the old one — preserving every quirk and behavior — but dramatically faster. This is the kind of invisible infrastructure work that makes TypeScript scale to enterprise codebases with millions of lines of code.

Press enter or click to view image in full size

Photo by Rob Wingate on Unsplash

From “Maybe 25%” to Total Dominance

Press enter or click to view image in full size

Photo by Eva Blue on Unsplash

When Anders Hejlsberg started TypeScript in 2012, his ambition was modest:

“I figured if we got 25-percent of the JavaScript community interested, that’d be a win.”

The problem they were trying to solve was practical: JavaScript was the backbone of the web, but it didn’t scale for large, multi-developer codebases.

Thirteen years later, TypeScript has far exceeded that 25% goal. It’s not just the most-used language on GitHub — it’s reshaped how an entire generation thinks about JavaScript development.

The language has accumulated 12 years of evolution captured in its GitHub repository. As Hejlsberg put it:

“We have 12 years of history captured on GitHub. It’s all searchable. It’s evolution you can grep.”

What This Means for Your Career

If you’re a developer trying to decide what to learn or which direction to take your career, this data provides clear signals:

For JavaScript Developers

TypeScript isn’t optional anymore. It’s not a “nice to have” or something you learn later. The industry has moved. Every major framework, every modern codebase, every AI-assisted workflow assumes TypeScript by default.

For New Developers

Consider starting with TypeScript instead of plain JavaScript. The learning curve is slightly steeper, but you’ll be learning the standard that the industry is actually using. You’ll also build better habits around thinking about types and data structures from the beginning.

Resources to get started:

• TypeScript Official Documentation
• TypeScript Handbook
• React TypeScript Cheatsheet

For Python Developers

You still own AI/ML work, but if you want to build web applications, APIs, or user-facing tools around those models, TypeScript is the language those systems are being built in. The modern stack increasingly looks like:

• Python for the model layer
• TypeScript for everything that touches users

For Hiring Managers and Tech Leads

If your team isn’t using TypeScript yet, you’re swimming against a powerful current. New hires expect it. Frameworks default to it. AI tools work better with it. The migration cost is real, but the cost of staying on vanilla JavaScript is compounding.

The AI Era Changes Everything

The story of TypeScript’s rise is really the story of how AI is reshaping developer tools and preferences.

In the past, choosing a programming language was about picking an IDE, framework, or paradigm. In 2025, that calculation now includes: “How well does this language work with AI coding assistants?”

The answer for TypeScript is: extremely well.

Type systems give AI-generated code structure and verification. They create guardrails that keep hallucinations from reaching production. They provide the semantic information that makes refactoring tools and agentic coding systems possible.

As Hejlsberg noted in his interview:

“AI started out as the assistant. Now it’s doing the work, and you’re supervising. It doesn’t need an IDE the way we do. It needs the services.”

Those services — type checking, semantic analysis, deterministic refactoring — are exactly what TypeScript provides.

Looking Forward: The Next Wave

The Octoverse data hints at what’s coming. Between May and September 2025, coding agents created over 1 million pull requests on GitHub. These aren’t just experimental side projects — the activity is concentrated in well-established repositories with significant star counts.

We’re entering an era where code is written by both humans and machines. In that world, types aren’t bureaucracy or ceremony. They’re truth checkers. They’re the contracts that let AI-generated code integrate safely with human-written code.

TypeScript’s rise to #1 isn’t a fluke or a fad. It’s a structural shift driven by fundamental changes in how we build software. The language that was supposed to be a “pragmatic fix” for JavaScript’s scale problems has become the foundation for the AI-assisted development era.

The Bottom Line

Press enter or click to view image in full size

Photo by Jan Tinneberg on Unsplash

Every second, more than one new developer joins GitHub. And increasingly, they’re choosing TypeScript as their language.

Not because someone told them to, but because:

• 🎯 That’s what the frameworks default to
• 🔧 What the tooling expects
• 🤖 What works best with the AI assistants they rely on from day one

The question isn’t whether TypeScript will remain dominant — the question is what comes after this. When AI can write code fluently in any language it’s seen enough of, when types become the universal interface between human and machine, when the next generation of developers expects AI-native workflows by default — what does the programming language landscape look like then?

For now, the data is clear. TypeScript is the language of 2025. And if the trends hold, it will define how we build software for years to come.

What are your thoughts on TypeScript’s dominance? Are you making the switch from JavaScript? Share your experience in the comments below!