Why AI is pushing developers toward typed languages – The GitHub Blog
January 14, 2026
It’s a tale as old as time: tabs vs. spaces, dark mode vs. light mode, typed languages vs. untyped languages. It all depends!
But as developers use AI tools, not only are they choosing the more popular (thus more trained into the model) libraries and languages, they are also using tools that reduce risk. When code comes not just from developers, but also from their AI tools, reliability becomes a much bigger part of the equation.
Dynamic languages like Python and JavaScript make it easy to move quickly when building, and developers who argue for those languages push for the speed and flexibility they provide. But that agility lacks the safety net you get with typed languages.
My instinct is like that of far better, more knowledgeable developers like Brett Taylor is that in time, large language models and coding agents won’t write languages that have been developed for humans (whether that’s JavaScript or Python or whatever). Instead, they will develop in languages that are optimised for the output of a large language model.
In the meantime, it’s certainly the case that we are putting languages developed for humans. The question is, which languages should we be using? There’s certainly debate about whether or not typed vs untyped languages work better with large language models. Here is a discussion of the issues around that.
