Systemd is actually way more reliable than other solutions. Forget things like cron and startup scripts. Systemd can monitor and automatically try to restart software.
Been using systemd for at least 6 year now, and yes it is indeed quite stable.
But making startup services is hot garbage, and accessing system logs is even worse. journalctl is an unapproachable mess, and I really don’t like the idea that systemd is kind of slowly replacing the linux kernel in its entirety.
It doesnt affect my day to day as a normal user, but when I switch to power user mode its… It makes maintaining my system very unenjoyable.
For me personally systemd is much better especially for services and logs. It creates a consistent environment and provides lots of features like sandboxing and failure detection. I really don’t like how some software dumps random logs everywhere and having a proper database is nice. Journalctl is tricky to learn but it is nicer than trying to manage text files.
We literally have /var/log/ as a well-known standard though. Almost every piece of linux-standard software dumps to a subfolder by the app name in there. Systemd should at the very least have the capability to mirror there so you can get at the logs in a sane way.
Systemd is actually way more reliable than other solutions. Forget things like cron and startup scripts. Systemd can monitor and automatically try to restart software.
Systemd hate mostly boils down to hating change
Been using systemd for at least 6 year now, and yes it is indeed quite stable.
But making startup services is hot garbage, and accessing system logs is even worse.
journalctlis an unapproachable mess, and I really don’t like the idea that systemd is kind of slowly replacing the linux kernel in its entirety.It doesnt affect my day to day as a normal user, but when I switch to power user mode its… It makes maintaining my system very unenjoyable.
For me personally systemd is much better especially for services and logs. It creates a consistent environment and provides lots of features like sandboxing and failure detection. I really don’t like how some software dumps random logs everywhere and having a proper database is nice. Journalctl is tricky to learn but it is nicer than trying to manage text files.
We literally have /var/log/ as a well-known standard though. Almost every piece of linux-standard software dumps to a subfolder by the app name in there. Systemd should at the very least have the capability to mirror there so you can get at the logs in a sane way.
I can’t say I agree but I see where you are coming from.