notabot

That does feel rther like jumping out of a plane and hoping you can finish making your paracute before it’s too late.

The concept of moving on from X11 is a good one, but making Wayland just a protocol that every compositor has to implement separately, and having so many optional larts to the spec seems like a guarantee that the ecosystem around it will never properly mature.

The KiCad developers have a good article about some of the issues with Wayland here.

Hmm, that one worked for me, but maybe the wayback machine will work for you? https://web.archive.org/web/20250618100950/https://www.linuxjournal.com/content/arch-linux-breaks-new-ground-official-rust-init-system-support-arrives

The article vanished some time after being published, here’s an archive link.

If you are just a user, in that a computer is just a tool you use, then you’re right, there’s comparatively little reason to be concerened or even know about the underlying details of the system. If you go further and start making changes to your system, or even building more complex systems, over time you will find yourself forming quite firm opinions about various parts of the underlying system, especially if you’ve had experience with other options.

Honestly, I’m not sure, I was looking at Devuan, but then noticed that Debian supported sysvinit natively so I went that route instead. I figure that sticking to the source distro was going to give me fewer headaches, and so far it’s been plain sailing.

Debian, installed without systemd as per the wiki. So far I’ve not hit any issues, whilst I’ve recently ended up diving through both kernel and systemd code to find the root cause of an issue I was hitting on one server. I could have just bodged past it, but I wanted to actually understand what the issue was, and what else it was going to affect.