The way I understand it is that the security team supports releases for 5 years. If you are running an older version of ubuntu than that and want security backports, you need to get the extended support. The difference in Debian is that when a release is too old, the security team simply doesn’t backport security fixes. You can pay someone to do it, but it’s not a part of what Debian as a project does.

That card game isn’t called that anymore, but 20 years ago it was the standard name for a well-known card game.

I wonder how much is philosophy and how much is not wanting legal troubles. Those things aren’t contradicting of course.

I had a lot of issues on silverblue using vscodium as a flatpak, I think I will try installing it in a distrobox instead.

if you program using vscodium, do you install a separate vscodium in every distrobox?

Hm, ok, so the official definition is: “It is characterized by loosely coupled systems that interoperate in a manner that is secure, resilient, manageable, sustainable, and observable.”

Nethack works well on Linux too.

What exactly does “cloud native” mean? I’ve used Silverblue and I get the immutability etc, but what is the definition of "cloud native?

It is sort of an anachronism. I’m not saying that we don’t need textual interfaces, but emulating a terminal from the 70’s is not the only way. Plan9 had textual interfaces without the need for an emulated terminal.

Some evenings, when a piece of code I wrote compiles on the first try and it all seems so straightforward and simple, I feel blessed by the Spirit of the Machine.

In these corporate times we can stay free, share the code, and help our neighbors. Together we can share the joyous spirit of friendship, hacking, and arguing endlessly over which distro is best. In conclusion, Linux provides us with many good things, and should be celebrated.

You used Linux two years before it was released?

I’ve noticed a pattern in distrohopping among my linux using friends. Many started with ubuntu back in the day, then switched to a less preconfigured distro like arch, gentoo, etc. You learn a lot being forced to tinker and fix things. But after that, many seem to have landed on distros of the debian or fedora kind, because they want to get actual work done and you can make any distro do almost anything anyway.

I don’t know about morality, but my view is that it’s part of the deal with free software: users can do what they want with it. If you willingly make your software free, that’s what you signed up for. In return, the devs have no obligations to listen to users or do anything they don’t want. If they only want to fix bugs in the flatpak, fine, that’s their choice. It’s their software, we’re all free to work on or use it as we want.

Plan9 would have some opinions about that.

I just feel that it’s technically wrong to call it x64. x86 is the architecture. The x belongs there, so x86-64 makes more sense, but not “x64”. It’s a marketing term, but it still bothers me.

Isn’t “x64” still an x86 architecture?

This reminds me of Rob Pikes paper from the year 2000.
http://doc.cat-v.org/bell_labs/utah2000/utah2000.html

If we want to do something radically different, there’s always gopher and gemini browsers.

Tumbleweed is not a derivative of Leap.