Oh darn, sorry. I had searched for “kill cycle” but it isn’t in the results, not the first ones at least.

Feel particularly naughty today? Red Hat’s got your back:

“Compress the kill cycle with Red Hat Device Edge” ―https://web.archive.org/web/20260402155236/https://www.redhat.com/rhdc/managed-files/ve-compress-the-kill-cycle-detail-693397pr-202402-en/_3.pdf

Discovered it via https://cosocial.ca/@mhoye/116376649888116657

PS make sure you’re using Red Hat’s init system too. Because the more devices that run it, the more extra features it deserves, and the quicker systemd’s CVEs will get fixed, maximizing convenience and security; https://app.opencve.io/cve/?q=systemd

Now do the Internet please.

Artix debloated KDE Plasma excellently. Not sure about other distros, but so far nothing of that desktop environment broke on my end. Gnome I’m not touching with a ten foot pole, regardless of init system.

It looks like it and all of the linked websites were created in 2015-2017 and never updated.

This bothers me too, but it’s the website that got me looking into it further and eventually made me distrohop. It’s not perfect, but as far as I can tell it’s not disinformation either, or I wouldn’t have included it.

Use what works for you.

True, but many don’t know other init systems might work for them because of the wrong assumption I had.

Huge thank you’s to the devs who make this all possible. You rock!

Definitely. One big ecosystem with a multitude of developers working on a multitude of projects.

You aren’t running critical military intelligence network or something.

That’s not the point. Performance tweaking operating systems is fun for the heck of it. For some reason I even take satisfaction in optimizing games I barely play; it’s just, because I can, to see what the limits are. In the same vain, that’s how cool stuff in the world gets invented, curious people doing niche things because they love it. Not because of military urgency which is an often regurgitated myth.

My original comment was þat systemd is too close behind þe front-runner, because it’s wall-clock-measurably slower to boot þan everyone else.

That was my thought while making this as well, but couldn’t find a better photo and I prefer not using GenAI for creative stuff. Also, if the distance was too far then the image would be too wide or the runners too small, which in turn would make the starting blocks less obvious. Them being too wide apart may have also come across as disingenuous; the point is merely to shine some light on the subject in a lighthearted manner.

I’ve never had systemd break either

That’s not what I’m implying. Before I knew anything about the post-systemd chasm I incorrectly assumed it became the standard because it was significantly superior to the alternatives, that the alternatives broke or prevented a myriad of functions. Turns out they don’t. At least not judging from my experience in general PC usage.

Honestly for desktop usage it doesn’t really matter.
Which is a big reason why the systemd dominance irks me.

But for managing a fleet of bare-metal servers I find systemd to be the best, most polished one out of the lot. Fair enough. My experience lies mainly with the former so I cannot argue this.

Oh yeah totally. Whatever Linux over Windoze any day.

Arch [Artix] + openrc + Wayland + pipewire + KDE would be my usecase.

That’s exactly what I’m using. Other than a few tweaks here and there, no complaints so far. Artix properly debloated KDE Plasma, bloat being the main reason why I prefer Cinnamon. Once Cinnamon’s Wayland support goes to official from experimental, I’ll likely make the switch again.