I have finally decided never to use dynamically typed languages in new projects. They are a recipe for failure. At least they are not compatible with my personality. The elegance of #Scheme and the ecosystem of #Python can be deceptive, but the trade-offs are not worth the pain.
Schemers are rare and typically very competent. But the Python people simply have to learn a proper language. #Gleam looks promising. Just need more scientific packages. Official bindings for #Nx might be a good start.
@sigismundninja As a python person, I played with Gleam a year or so back and quite liked it.
Would I adopt it now? No way - it's far too small and not widely used enough. If it takes off, I might do. I got burned already with Elm several years back :D
Also, your decision is good for you, but "language X is crap, learn Y" is a very dull take these days. Python works for a lot of use cases, and saying python people "need to learn a proper language" is ... well ... I think you already know.
@michjnich Yeah. I just got extremely tired of debugging large (not that large) python code bases. Ty makes life easier, but it is far from perfect. And uv makes project management manageable.
We would've saved so much time by just using Go or even Rust. Probably.
@sigismundninja I get that.
Think about _why_ there are so many large python codebases though :) Also, debugging any large codebase can be a pita ime, if you're not familiar with it.
I do think typing will become more important with AI tools though.
I'm personally not a fan of Java, but I don't tell Java folks to go "learn a proper language" ;)
Maybe see you at the python meetup or over beers to discuss in more detail sometime if you're in Stockholm :)
ᛋᛁᚵᛁᛋᛘᚢᚾᛑ ᚾᛁᚾᛃᛅ
Michael J. Nicholson