Also the graph is pretty much zoomed in. It exaggerates the differences between the bars.

Admit it. You just zoomed in to see how accurate the recursion really is.

Initially the bug report was shot down by systemd developer Luca Boccassi of Microsoft with:

Emphasis mine.

While MS at least tries to be good guy nowdays, I just can't trust their code too much.

sudo is a setuid binary, but it’s a fairly simple program

Some people would disagree to this.

The brief description of run0 already has too many potential points of failure.

If the "listener" is PID1, which will run the privileged command, in theory, it would be quite bullet proof (in a working system PID1 is always there). But since this is systemd, PID1 is much more than that and much more complex. On the other hand spawning another daemon from PID1 to be the "listener" makes it, perhaps, even more complicated. You'd have to make sure the listener is always running and have some process supervisor there to watch if it exits... and maybe even a watchdog polling it to make sure it isn't frozen.

So my conclusion is the same as yours:

a solution in search of a problem

We already have a working solution. Have a well written SUID program. I've been using doas for some years now. It's simple enough that I trust it.

Predictions of which will win the race?

• noveau being useful with new nVidia GPUs
• we'll reach the year of Linux desktop

Yeah.

At maximum a bug/issue tracker is needed.

There's no any kind of announcement that pfetch is no longer maintained. My guess is: "it's ready".

EDIT: Looks like Dylan has been "offline" for some time...

Phoronix thinks I'm using ad blocker. In fact I'm not. I don't have any kind of adblocker on my network... *sigh*

If systemd works for you and you don’t know or care about the philosophical side of the argument, there is probably no benefit for you in switching.

Exactly this. There are few techincal problems with systemd, but those are so miniscule. I say this as an OpenRC+openrc-init user.

It's pretty maintenance free.

The following will make the experience a bit more seamless:

• use stable packages
• use sys-kernel/gentoo-kernel or syskernel/gentoo-kernel-bin
• use sys-boot/grub or better yet sys-boot/refind which auto-recognizes the latest kernel in your boot directory

I don’t mind a complicated install

After you have "installed" Gentoo there will be quite lot of installing of different programs to build your own customized distro. However if you yse systemd you'd get quite a lot in one strike, since systemd contains a whole lot of the central core components, like system logger (journald). The other route is to use OpenRC and with it sysvinit or openrc-init and choose the rest of the components.

Asking your question (the one I'm replying to) at the Gentoo forums may give you better answers and tips how to build maintenance free setup.

I've used Linux since about 2004 for personal use. On my homer server(s) and desktop. 95% of them Gentoo (stable). For my relatives I've installed some EL workstation distro. Especially my father needs a install-and-forget system, which Windows isn't.

But I do install and fix Windows PCs at my work. It's because how Windows works (or rather not work) I get paid. That said, the more I use Windows the more I get frustrated with it.

One of the worst things lately was the accidental activation of BitLocker. It got activated even when the user didn't have Microsoft account (from where he/she would retrieve the encryption key to decrypt the data if Windows decides to lock the drive). "Oh I'm sorry, but because M$ fuckup your data is gone. Do you have backups? 😇" To avoid any BitLocker issues the secure boot should be disabled. BitLocker shouldn't then be available for activation.

Some of the frustrating sides of Windows can be avoided by using Pro version of Windows. But that's simply not enough.

IMO the only reason to use (suffer from) Windows is if you play some games that require it.

... but there's an Atari sticker. Bothers me!