Engineering brief
You Think Languages Change Fast. Here’s the Data That Proves Otherwise.
This engineering brief covers You Think Languages Change Fast. Here’s the Data That Proves Otherwise., with practical context for AI and developer-tool decisions.
The Brief
Programming languages are not evolving fast; they are consolidating. AI LLMs are making this worse by favoring whatever language has the most training data.
Decision relevance
Read this for workflow impact, implementation trade-offs, and the claims that need technical scrutiny before they reach team planning.
Summary
Henney makes a data-backed argument that mainstream programming language adoption is far slower than the industry narrative suggests. Using three independent rankings (TIOBE, RedMonk, IEEE Spectrum), he shows the top 10 is dominated by languages from the 20th century. Python, Java, C++, and JavaScript have held the top spots for years. The tail is long,
but the head is remarkably stable. Most new languages are out in the long tail. Even Go and Rust, often considered new, are over a decade old. The core innovations—control structures, coroutines, functional features—date to the 1960s and 70s. Languages today borrow heavily from old ideas rather than inventing new ones. The rate of change
in the mainstream has slowed because there is too much existing code and too many jobs built around it. The major twist: AI LLMs are now consumers of programming languages. They write code in proportion to the volume of training data they've seen. This creates a feedback loop that entrenches Python, JavaScript, and TypeScript. Anders
Hejlsberg is cited: new languages are systemically disadvantaged because AI can't generate reliable code for them without massive datasets. The practical implication is that teams should not bet on language disruption. The barrier to entry for a new language in the mainstream is higher than ever. Investment in tooling, training, and AI integration for existing
Why It Matters
Language strategy is a 10-year bet; the window for disruption is closing fast.
Editorial analysis
Key claims
- Bet on incumbent languages. The AI feedback loop entrenches Python and JavaScript.
Practical use cases
- Use this as input for tooling evaluation, workflow planning, and technical due diligence.
Risks / caveats
- Claims that a new language will displace Python or JavaScript soon. They won’t.
Who should care
- Engineering managers, tech leads, and CTOs evaluating AI or developer tooling decisions.
Related topics
Bottom Line
Bet on incumbent languages. The AI feedback loop entrenches Python and JavaScript.
Watch
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
Your Platform Is AI's Trust Boundary, Not Its Replacement
Platform engineering becomes AI's trust boundary: without deterministic, API-first, compliant services, AI agents bypass or break things.
AI code generation is cheap. Validation is the new bottleneck.
The real AI bottleneck isn't generating code but validating it when no human reads it. Teams must build trust through testing and observability.
Robotics Hits Its 2021 Generalization Gap, Not Its 2022 Deployment Point
Generalist robot policies are moving faster than expected from pre-training to few-shot generalization, but production-grade speed and reliability remain an…
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.