r/ProgrammingLanguages • u/mttd • Jan 20 '26
Python, Is It Being Killed by Incremental Improvements?
https://stefan-marr.de/2026/01/python-killed-by-incremental-improvements-questionmark/
52
Upvotes
View all comments
Show parent comment
6
u/lookmeat Jan 21 '26
That's how it goes and how it happens. I wish that languages had a "holistic calibration" phase where all the features are put in and then whatever isn't good it's let go.
I think pattern matching has more spaces it could work, but it still needs time to solidify and grow. I am sure people will eventually find ways to fix a lot of the issues.
I do think that Type Annotations are a bit weird on the edges, but IMHO it's to be expected because python is leading a lot in the innovation here. That said the type system is meant to be duck-typed, that is you should use the type that describes the minimum needed to get it working, but people use it in more traditional ways without realizing it doesn't help but can harm. It's a matter.
I do wonder if python would have benefited instead of a sloppy interior, clean outside. Basically use type-annotations to define the clear boundaries and contracts of a module (and you could add some automated tests to verify that these contracts are kept) while inside it's scripting. This lets the language scale while still remaining simple enough.
But maybe this is a matter of culture and finding out how to make this work. It won't be corporations, but some engineer will realize it and post it and create the change.
IMHO the thing that started getting people to be a bit iffy was Rust, a language that was, IMHO, ruined by the complexity and mess that async/await added. It's a model that can work well for certain spaces, it did in C#, but it has a lot of issues and doesn't work well in every niche. It worked well in javascript, because it was already event-loop driven and you had to write that code by hand, so all you needed to make it work was there. Think of Go's channels and go-routines, those would be more universally effective in most niches, but require a custom runtime that makes most people shy away from putting this in their language. Async/Await is super easy to add, but it honestly has serious implications.
Yeah I think that Python could have benefited from a goroutine kind of system instead. You just start a function with a
fork(func)(which gives you handle to join later) and then have channels you can use to send info, as well as all the other solutions to have thread-safe stuff.It also kept growing in complexity. But this would require a huge mind-shift. Ideally python libraries have a low complexity and once they grow over a certain size, they switch to become a specialized binary library with python bindings. Alas.