Same month, both hit record contributor counts on GitHub.**
Not a contradiction. The ranking is just measuring the wrong thing now.
TIOBE tracks Google searches for a language name. That signal died with ChatGPT — Stack Overflow's question volume is down ~78% since launch. We didn't stop asking questions, we stopped asking them in public. The crawler just can't see a chat window.
So forget the index. Look at what's actually shipping:
Python is winning the model layer, and it's not close.
- Transformers pulled 43.4M installs in a week vs 1.8M for the JS build. 23:1.
- OpenAI's Python client: 97.7M weekly. The npm version: 31.8M.
- vLLM, SGLang — Python on the outside, CUDA underneath. It's the control plane for every expensive GPU in the building.
TypeScript is winning the product layer, and the reason should sound familiar to anyone pairing with an assistant daily.
- It passed Python for #1 in GitHub contributor count last year.
- Growing 67% YoY vs Python's 49% and plain JS's 25%.
- The compiler catches the model's wrong guesses (bad signature, wrong field name) before runtime. Untyped code finds out in prod, at 3am, from a log.
Then TS shipped a Go-rewritten compiler in v7 this July — type-checking VS Code's own codebase went from 125s to 10.6s. The tax for type safety just got cut 10x in the exact year assistants started depending on it.
Even the labs' own tooling shows the split: Claude Code is TypeScript. Codex CLI moved from TypeScript to Rust for speed. Nobody's reaching for Python to build the interface.
The "versus" framing is dead. These two stopped competing for the same job around 2023.
Python owns training, fine-tuning, serving, research.
TypeScript owns the agent loop, the tool calls, the thing the user's thumb touches.
Curious where the room lands on this — if you're picking up a language this year, are you picking it for the model or for the product? Genuinely think that's the only question that matters now.
Top comments (0)