that's what I mean, they haven't had any massive break in backwards compatibility for a while. I did get annoyed by it before and attempted to create my own language/platform - if need be, I have a basic setup of imgui/chibi/c-ffi that I could expand into something useful for scripting that isn't likely to break, but honestly it's such a massive amount of work compared to a conda env so I don't mind sticking with python for now. there's also micromamba which is a lot faster for the solver.

I can't hear you over the sound of pycache directories getting created just anywhere a .py file happens to exist. What genius thought that was even remotely sane? :) You can't hear but I'm being more lighthearted now but really I have no use at all for that shit language.

(yes I know it's configurable, but it also only behaves reasonably when & where that config is in place, not by default. It's opt-out vs opt-in)

I don't really like reinventing the wheel in yet another shiny language, so I'll stick with what works for now. and if I do decide to migrate, it won't be to anything other than C/lisp.

I am literally sitting at a console login because upgrading ubuntu from mantic to noble yesterday destroyed my entire system...because of python 3.12.

The apt output had a ton of errors about py scripts with invalid syntax, and those scripts failing apparently broke everything else and half the system basically got uninstalled, and most of what's left doesn't work, half the services other startup actions failed. Even the login message is broken with python syntax errors. Don't even have network to fix it, even wired let alone wifi. It's reinstall time.

This is today 2024, not during some 15 years ago big transition, and the scripts that broke are all fully packaged and package-managed parts of the os, not even random normal end user written.

This is not remotely a problem of the past and it's all better now and "have you used it lately?".