Unix grey beard here.

Yes. Distros with systemd are simply easier to maintain.

You won’t ever get me to care about what init system I run on my machine. I just need it to work.

Systemd is fine but I am kinda sad that it’s ubiquity has resulted in increasing dependence on it.

I really like void linux which uses runit and it seems like its getting harder for things to work without systemd. Gnome made some changes fairly recently that increase dependence, I hope devs can build ways for gnome to still work :/

My only real criticism is that using runit makes me feel like systemd could be a lot smaller and more elegant. But using systemd has never caused me any problems as best I’m aware 🤷‍♂️

Where did all the Pöttering hate go?

No one cares about systemd at this point

If you want to use your computer like it is 2005 go for it. Just don’t keep bringing up this dead topic.

One thing the author probably hasn’t done yet or just doesn’t mention is that you can configure .container services with systemd-podman units (often called quadlets), e.g. a simple MariaDB container would look like this:

[Unit]
Description=MariaDB container

[Container]
Image=docker.io/mariadb:latest
Environment=MYSQL_ROOT_PASSWORD=rootpassword
Environment=MYSQL_USER=testuser
Environment=MYSQL_PASSWORD=testpassword
Environment=MYSQL_DATABASE=testdb

[Install]
WantedBy=multi-user.target

Short intro Full reference

This is superb, because it means your containers finally feel well-integrated with the rest of the OS and you can use systemctl, journalctl, etc. just like you would with other services.

Personally, I use this as an alternative to Podman/Docker compose and have been very happy with it running rootless containers from Nextcloud, Pufferpanel, Forgejo, Authentik, etc. (ask me for .container files if you need any help, I’m currently working on a small repo with a collection)