... and no, this isn't me overreacting because I had a crappy day. This frustration has been building for years.
I read a really great article years ago about culture and motivation in open source projects and how perverse incentives - attracting new community members with new shiny trendy things - not really caring about the existing user-base - causes exactly this kind of pointless upgrade treadmills and wasted engineering effort.
I wish I could find that article again. It was so right.
What I *should* do, is figure out how to wean myself off Python.
I think #golang is probably where I should go.
A modern C-like language with high level features. Written by old curmudgeons who haven't got time left for busywork. Who value the promises made by their APIs and design choices.
Evidence: the security community lambasts them for refusing to change an API which was deemed "not secure enough." https://www.bleepingcomputer.com/news/security/critical-golang-xml-parser-bugs-can-cause-saml-authentication-bypass/
That, kids, is a feature. Not a bug.
My kind of people!
in 2017, Russ Cox wrote in #golang a 2fa tool that i use daily. since then, he touched it 3 times:
https://github.com/rsc/2fa/commits/master/
meanwhile, all of my Python projects break in every new Python release.
@HerraBRE I think you will like it! It鈥檚 pragmatic first and foremost.
@HerraBRE try uv, I鈥檝e hat luck using it to stabilize that exact problem.
@jaseg Really, no.
Unless uv has a feature that magically makes the CPython community stop deprecating things.
But it is exactly this mentality, thinking that people can just tool their way out of a culture of instability, which is why I should have walked years ago.