@mischievoustomato @anemone @Ghislaine

It's this time again :blobugh: So I'll make it short.

I've used it for years and found numerous somewhat serious bugs in it. For example, the dependency resolving was broken for some time in a release, which meant some of the services would not start at all and would need to be started manually. Timer overrides weren't being applied meaning that planned jobs wouldn't run as planned.

I've read the "Windows 10 Creators Update issue for systemd" where due to a poor documentation, it deleted /home folders. A long time maintainer went "working as intended, closing issue", closed pull requests fixing the docs, or temporarily disabling the functionality. And after people complained in the GitHub issue, he went onto Mastodon and called it overblown drama created by Internet drama seekers. He did the same when systemd broke hybrid sleep functionality.

I've tried to compile multiple releases from scratch with most of the features disabled, because I needed to read journals from a different machine and some other completely basic functionality. And what I received was hours of finding fixes for the build-breaking bugs in stable releases and manually fixing some. They seemingly don't test basic build configuration.

And guess what doesn't have these problems. OpenRC. It has one long-standing bug with swap file mounting that is a single line change and a one-line edit to the PKGBUILD away and most people won't even notice that, unless they use a swapfile on a BTRFS subvolume. Same with any BSD rc system. Do you need service supervision? We have a thing for that. It's called daemontools or FreeBSD's daemon.