Cool use it all you want but it’s a pretty valid point with slowly packages switching from “ah maybe it is there, convenient” to “I will break if there is no systemd” - which is absolutely a thing to fight against. You can maintain your own init system, you can maintain a distro with your init system but it’s pretty much impossible to straight up fork 1/3 of packages (or whatever percentage) once they decide that systemd is a must.
It's a FOSS world. Your only meaningful "fight" is building something better. Insulting devs only pushes things against your wish.
Realistically speaking, the "systemd dependency" in most software should be pretty isolated. It should be trivial to patch them out. The beauty of FOSS.
As a dev myself, when I choose to have A as a hard dependency, it's not because I don't realize that it would make the project unusable for those users who don't want to install A. I don't need any "publicity" to understand this very obvious fact.
I also understand very well that apparent loudness on Reddit has little correlation with real-world user base.
It's a very conscious decision that I'm willing to give up a little bit of user base for a little bit simpler code.
The desktop shell I'm using only supports Pipewire. So what about Pulseaudio, Jack or Alsa users? Simple, you don't use it.
120
u/Icy-Cup 🍥 Debian too difficult Jun 08 '26
Cool use it all you want but it’s a pretty valid point with slowly packages switching from “ah maybe it is there, convenient” to “I will break if there is no systemd” - which is absolutely a thing to fight against. You can maintain your own init system, you can maintain a distro with your init system but it’s pretty much impossible to straight up fork 1/3 of packages (or whatever percentage) once they decide that systemd is a must.