It's interesting in the sense that something went catastrophically wrong here.
This isn't just a small indie dev wasting a bit of money, it's hundreds of millions set on fire by an established company in this industry.
The fact that "no one heard of it" is exactly the point. What went wrong here?
It only started this year for me (had this number for 15 years or so), and it's mostly numbers from the UK and India for some reason (I'm in Germany).
Doesn't work, unfortunately. It seems to be a 16bit app.
No, it's pretty obscure, I barely managed to find it at all.
I use Karch, btw.
We could start by not requiring new chips every few years.
For 90% of the users, there hasn't been any actual gain within the last 5-10 years. Older computers work perfectly fine, but artificial slow downs and bad software cause laptops to feel sluggish for most users.
Phones haven't really advanced either. But apps and OSes are too bloated, hardware impossible to repair, so a new phone it is.
Every device nowadays needs wifi and AI for some reason, so of course a new dishwasher has more computing power than an early Cray, even though nothing of that is ever used.
Usually ~/devel/
On my work laptop I have separate subdirs for each project and basically try to mirror the Gitlab group/project structure because some fucktards like to split every project into 20 repos.
Ansible is actually pretty nice, if you get the hang of it. Not perfect, but better than triple tunnel ssh.
You could simply automate step by step, each time you change something, you add that to the playbook and over time you should end up with a good setup.
Flakey dev setups are productivity killers.
The real question is why you're torturing yourself by manually fixing that stuff? Don't you terraform your Ansibles?
Imagine being a doctor in this scenario. You could save them. You have the tools, the capabilities, the facility. But you have to let them die or risk ruining your own life. There are no winners here.