@davidrevoy regarding Wayland pains:¹ I think that is a cultural problem in many Free Software communities: "someone else has to fix the mess I made".

I’ve also been warning about this for years. But it’s hard:

draketo.de/software/volatile-i

That even you haven’t gotten through to people is harsh.

Where it hit me the worst is with Lilypond dependencies. We narrowly avoided a fallout between different communities there and I now regularly remind people to keep it in mind.
¹ davidrevoy.com/article1030/deb

 There’s the core tenet: do not make your software volatile — Wayland makes other software volatile: after an update, things are broken. And complex tools are the ones most likely to get broken.

I had hoped that we learned from the Python 3 debacle: it took over a decade for Python 3 to become widely adopted and even today there are many specialist tools that require Python 2.

Yes, those tools are not well-maintained, but they work. They solve real problems.
Some small migrations are usually done by distributions who then upstream their changes, but that’s it. This is a strength.

Regular breaking changes to the infrastructure threaten that.

We cannot stand on the shoulders of giants if we constantly break old tools.
0

If you have a fediverse account, you can quote this note from your own instance. Search https://rollenspiel.social/users/ArneBab/statuses/114615456607020349 on your instance and quote it. (Note that quoting is not supported in Mastodon.)