Bisexual_Cookie

I haven't seen much of a problem from any of their users

Yeah, didn't know it was a thing but that would make sense

Momentum, support and compatibility.

There are also other OS'es like FreeBSD and openBSD that are relatively widely used and a whole host of vendor OSes like IBM's IAX or Z/OS or the open solaris derivative illumos (all unix based), not to mention the embedded real time OSes that you find in a lot of cameras and such.

The common thing among most still in use is that they are old, well tested, stable, have a lot of software developed for them + they are in most cases compatible with a lot of different hardware, these things need time and money to achieve and people aren't going to develop software for an OS that isn't going to be used because it lacks those features.

That's not to say people aren't still writing new operating systems, they definitely are, it's just that they'll never get as generally used or well known as the mentioned 3.

I've been using wayland almost exclusively since 2020 because x-org doesn't support multi refresh rate setups and it was driving me nuts to have everything run at 60hz. It's been pretty smooth sailing because I use an AMD gpu. I have to admit that steam is indeed a lot buggier under wayland, I try to use gamescope for every game as that fixes most problems I have with them. My hope is that proton will use wayland for most games by the end of this or next year.

Debian's wiki states that "Wayland is used by default in Debian 10 and newer" (on gnome, It's also the the default for plasma 6 but that'll take some time to get into debian as you say)

Ubuntu core would work for this. Is this a security critical setup? Otherwise I don't see why you would go immutable, if you just want a nice base for hosting containers I'd recommend dietpi running something like casaos (or just plain docker). You can set up auto upgrades pretty easily in dietpi!

wow that's awesome! :)

as others have pointed out, you can use systemd-cryptenroll to add your tpm as a way to unlock the disk at boot, security of this should be fine if secureboot is enabled (for this to work it will need to be anyway) and a password is set for the uefi. See the archwiki entry for setup info (command is as simple as systemd-cryptenroll --tpm2-device=auto /dev/rootdrive, also the device needs to be encrypted with luks2, no idea if zorin uses that by default but you can convert luks1 to luks2 {backup ur headers first!})

Allright

Is the bulletins site no longer updated?