I've used Linux for over 20 years at this point, my first Linux computer was a PS2 console and my second one was a PS3 console. I remember the rc scripts and upstart, and I hated dealing with any of it, systemd, its timers and the user units were the most convinient change in decades. I hear so many anecdotal accounts of "sytemd destroying someone's system", yet personally it was nothing but a pleasant experience.

I think there's always needs to be an alternative, and I welcome anyone who's actually building alternative code paths and doing the work to create the alternative tools, but every time some tool gains a dependency on systemd to improve the functionality and the mob comes in complaining I can't help but get angry. It's open source. You can patch it. You can switch to something else, but instead you hurl insults at people volunteering their time to make software you run better.

I don’t care. I have run Linux machines since 2001 and systemd is one of the least offensive reinvention of the wheel I have had to deal with. All software is shit one way or another, all that matters is how much effort do I have to spend to find myself dealing with another, unsupported pile of shit.

> What most systemd critics consider "bloat", I consider necessary complexity to solve a complex problem generically.

I think the issue people took with it was less on technical merit and more about the principle of resisting a change which was occurring too quickly for comfort

it was kneejerk reactionary to begin with and hasn't made any more sense as systemd has improved and received better integration with other software

I do mourn the loss of Upstart though, I thought that was one of Canonical's cooler projects

I also use Void/runit primarily and enjoy it because of its simplicity, it's a nice _exercise_ to run systemd-free but I don't pretend it comes anywhere near the level of capability that systemd provides

My home lab requires:

* Option 42 (custom NTP configuration)

* Option 66/67 (TFTP/PXE boot)

* Option 119 (Domain Search List)

* Vendor-specific options (43)

* Option 121 (Classless Static Routes)

* Custom enterprise options

+ DNS name Regex replacement (iPod/WII/Lucent DSLAM)

In RedHat dominated network, NetworkManager remains the dominant choice for:

* Enterprise desktops

* Laptops

* Many enterprise servers

* Complex managed networking in the Red Hat ecosystem

RedHat is still struggling to replace my network-manager's ultimate stackable network interfaces (VxLAN-VLAN-Bond-GRE-IPSec).

Furthermore, it isn't about hate. It is about KISS: it is about keeping PID 1 as simple as possible, something that all embedded systems and secured system should still aspire to do.

PId 1 should be pro forma and semantically secured as possible with minimal dependencies.

And process certainly should not be default all-privilege.

Simplicity of integration over complexity.

A bit of context: My specific case is creating timers (similar to crontab). I'm shuffle-playing music playlists at certain times of day. I'm comfortable with terminal/command-line, however the computers I'm building out are used in maker-spaces, where many people are not super technical. This has got me into the habit of thinking "what's the 'easy mode' for a lot of tools. For example, GitHub Desktop is a great way to slow-roll people into using `git` if they have never used it before. I like tools like that. Let me know what you suggest.

Guaranteed that the replacements would have a combined list at least as bad.