My personal reasons for disliking systemd (note: I still use systemd):
The lead developer of systemd has said multiple times that we should be fine with break POSIX if it means developing faster.
systemd has massive attack surface, making it easier to exploit and result in privilege escalation. It is a highly complex and large codebase that really shouldnt be given the trust of PID 0
systemd is not portable or modular.
It only just barely got musl support. Hope to see it improve in the future.
systemd is much slower than other inits (eg. dinit, s6, openrc)
systemd being the go-to init encourages developers to more heavily depend on it, making it difficult for distros without systemd
The biggest feature I like about systemd is run0, though I wish it was a drop in replacement for sudo. Secondly, I do like that services can be sandboxed.
It’s developed for linux and there is literally 0 linux distributions that are POSIX-compliant, also standard is dead.
It doesn’t, also moving it to any other PID won’t make any difference.
It is modular (IIRC there is only three mandatory parts) and portable.
Was completely on musl side (also musl is as much not portable and modular as systemd 🙃 and in every practical way worse than glibc).
It’s not an init, nor does it present itself like this. Do you have any benchmarks that show this slowness when doing comparable operations?
Why exactly depending on a stable system component is a bad thing? Distros without systemd are moving against the stream, obviously there going to be some problems.
My personal reasons for disliking systemd (note: I still use systemd):
The biggest feature I like about systemd is run0, though I wish it was a drop in replacement for sudo. Secondly, I do like that services can be sandboxed.
I mean, so does GNU.