Here's a prediction: not even fedora will drop it by 2027.
Wayland still doesn't work for a lot of people, and the ecosystem is nowhere near mature enough. I doubt enterprise distros will consider dropping xorg until their users can actually work on Wayland.
IMO too much "Tutorial", not enough Review. For example:
The spectrwm workflow is unique. It took me awhile to become acquainted with the standard flow and gain comfort in using it. I did have to bend, fold, and spindle the environment a bit
You haven't written a single word on how it's different from any tiling manager, nor what and why you changed.
Generally the article feels like the first comment in unixporn, where you list out your relevant dotfiles. The only extra information is that you like it, and a list of dependencies for your config.
Oh no, a wm might die in a few decades! Anyways...
Tumbleweed is recommended often here.
I occasionally try out Opensuse since like 2007, but I always find the alternatives better. Why Tumbleweed over Arch, why Leap over Fedora/Debian, why suse over RHEL?
Is any popular stable distro free from corporate influence aside from Debian?
This shows something else. The traditional languages are all more common than Rust.
It's a survey from 2019, but in those rust is traditionally the favourite language nobody uses professionally.
I suppose Go could be a good competitor, and I read a thread comparing C=Go, C++=Rust.
Go's syintax is C inspired, but it's not made to replace it, nor do they compete in the same space.
Look at zig instead of you're interested in that.
I am interested in a discussion about that, as I would like to learn one of these languages
Skip rust unless you have years to get good at it.
TIL GPL is a proprietary licence
You never saw an IRC chatroom archive?
If you're running unstable system packages, immutability won't really save your stability.
So don't complicate it, and just use Debian with nix and home-manager. That way you have a stable base, and you can create a list of bleeding edge packages that should be installed. In any case it should be essentially only docker + whatever can't be dockerised.
Debian + nix unstable and you get the best of both worlds. Bleeding edge userland, and the system always boots^btw
AFAIK no distro forces you to reboot, but they all require it for some updates to take effect. You can't reload the kernel while the system is running.
Fedora just makes that clearer to the user by only installing those updates when they're going to be active - after a reboot. I think it also blocks new system updates until the current set is completely finished.
You can disable offline updates in the system settings, but I think they're a good idea, especially for the average user.
Sudo apt... is not the problem. Home-manager and a list of packages are so much better and easier to manage. That's why I'm currently running nix on top of Debian.
The problems start when you want to modify something, or when you want to use tools that expect fhs complience. Then you run into a skill mountain and discover that the documentation is not great.
At least that's my experience with guixos and nix. I haven't tried nixos, and if I do, it'll be only to generate docker images and such.
For a workstation, in most cases, there are simply not enough benefits to deal with the bs that comes with a declarative os.