For years, the default advice for anyone choosing a first or second programming language was simple: learn Python. It's still the most widely taught language and tops the TIOBE index. But several major developer surveys this year point to a real shift underway, and TypeScript is at the center of it.

What's Actually Changing

In Stack Overflow's most recent large-scale developer survey of roughly 65,000 developers, TypeScript overtook Python as the second most-preferred language, trailing only Rust. TypeScript has also become one of the most active languages on GitHub by monthly contributor count, a shift driven largely by its dominance in modern web and full-stack development, where JavaScript-based frameworks remain the default choice.

Part of what's fueling this is the rise of AI coding assistants. A widely cited 2025 analysis found that a large share of errors generated by AI coding assistants were type-related — exactly the category of mistake that TypeScript's static typing catches automatically, before code ever runs. As more development teams lean on AI-generated code, that safety net has become more valuable, not less.

Should You Switch?

Not necessarily, and definitely not by dropping Python. The two languages solve different problems:

• Python remains the dominant choice for data science, machine learning pipelines, scripting, and backend services where rapid iteration matters more than compile-time safety.
• TypeScript is increasingly the default for anything customer-facing on the web — frontend frameworks, full-stack JavaScript applications, and teams that have decided type safety is worth the extra setup.

Where the Job Market Is Pointing

If you're already a JavaScript developer, learning TypeScript is close to a no-brainer at this point — a large share of new frontend and full-stack roles now list it as a requirement rather than a nice-to-have, and the migration path from JavaScript is gradual rather than a rewrite. If you're starting from scratch and weighing your first language based purely on job postings, the honest answer is that both remain safe bets, but for different kinds of roles: Python if you're aiming at data or ML-adjacent work, TypeScript if you're aiming at product engineering.

The Broader Pattern

What's really happening isn't Python losing relevance — it's the market maturing into more specialized lanes. A few years ago, "learn to code" meant picking one general-purpose language. Today, the more useful question is which lane of software work you want, because the tooling, the typical salary band, and the day-to-day work look increasingly different depending on the answer.

If you already know one of these two languages reasonably well, the better investment right now is usually depth in your existing lane rather than breadth across both — unless the specific roles you're targeting explicitly call for the other.