This should be renamed to "Branding about..."...Because that seems to be the focus on this destination webpage...and not content specific to the underlying tech of systemd.

> systemd is a suite of basic building blocks

So was linux before systemd.

Choice is good.

https://linuxstans.com/best-linux-distros-without-systemd/

https://www.without-systemd.org/wiki/index_php/Main_Page/

https://without-systemd.org/wiki/index_php/Linux_distributio...

I can recommend the book "Savaged by Systemd"

It's on AA

"Building blocks" makes it sound like things you can use to build other things. In reality it's more of an octopus, or a fungus.

We had reasonable building blocks before systemd...

undefined

This is just the homepage. Bah. I was hopeful this might be more! I would genuinely love for some posting on systemd that can actually talk to this.

There's posts on using systemd for this or that, which are fine, but it feels like the pro-systemd camp doesn't find or make opportunities to rally, to express ths vision, where-as the anti-vision (as ever) sells itself, is a magnet that makes common party out of all dissent.

Where "basic" follows a highly nuanced alternate definition, where if you step out of line without realising it, you lose 3 days debugging a complex undocumented interaction between 4 enterprise crapware daemons only to find out the answer is "you're wrong and won't fix" buried in a 6 year old bug report, when all you did was plug in a USB mouse or try to set the default audio output device, or something else.

Total and utter propaganda, it's underdeveloped steaming garbage

Yeah, and these LEGO blocks are strewn around the room by a 3-year-old just waiting for you to step on them. It's the worst thing, there is no organization in systemd. No rhyme or reason to it.

The basic core service supervision in systemd is great. And nearly everything else around it is bad as a result: command-line utilities, filesystem mount handling, virtualization integration, network configuration, etc.

Just look at systemctl's `--help` if you don't believe me. Why does it have `service-log-level` to set the log level for the target, but not a way to actually _view_ the logs? Or why does it have a top-level `--firmware-setup` flag?