Apple can maintain launchd alone, they don't have distros to deal with. It's up to the distros to decide how much they want to use systemd and it makes sense for debian to be only systemd if they want.
That said, having used systemd on Ubuntu and having not used it on Gentoo: I've yet to see a feature in systemd that isn't currently well done by existing programs I use on Gentoo. I don't want the init system dealing with cronjobs, cgroups, logs, sockets, or even services I don't want to start at boot. I don't like some of the defaults systemd has, and thus also don't like giving up any control over configuration of what I might want to do. Any init script has root, so it should be the app/user which decides which cgroup config to run in and the init system should not be involved at all. Break all of this functionality up into completely separate projects, and let app developers/distros decide if they want to use it.
I wouldn't mind writing init scripts in a declarative way with better dependency management/parallelism, but that's really all I want from an init system. Fixed device naming works just fine on eudev/openrc/elogind, and I honestly don't know why I would want systemd on Gentoo.
Pulse audio for what it's worth, does enable features I use like pulse effects. The same is not true for systemd. It's bloat I don't need, and get by without just fine using plasma/kde on the newest kernel/gcc/etc..
That said, having used systemd on Ubuntu and having not used it on Gentoo: I've yet to see a feature in systemd that isn't currently well done by existing programs I use on Gentoo. I don't want the init system dealing with cronjobs, cgroups, logs, sockets, or even services I don't want to start at boot. I don't like some of the defaults systemd has, and thus also don't like giving up any control over configuration of what I might want to do. Any init script has root, so it should be the app/user which decides which cgroup config to run in and the init system should not be involved at all. Break all of this functionality up into completely separate projects, and let app developers/distros decide if they want to use it.
I wouldn't mind writing init scripts in a declarative way with better dependency management/parallelism, but that's really all I want from an init system. Fixed device naming works just fine on eudev/openrc/elogind, and I honestly don't know why I would want systemd on Gentoo.
Pulse audio for what it's worth, does enable features I use like pulse effects. The same is not true for systemd. It's bloat I don't need, and get by without just fine using plasma/kde on the newest kernel/gcc/etc..
Comment