3 ms·
> systemd provides a lot more than spawning processes at boot. And that is exactly what I think is the most irritating thing about it. I just want it to init m
by mverwijs 12y ago
> systemd provides a lot more than spawning processes at boot.
And that is exactly what I think is the most irritating thing about it. I just want it to init my system. I'll do the rest, or decide which piece of software should. NOT the systemd developers.
- Xylakant 12y agoThe systemd developers don't decide that. They offer capabilities. Obviously the value proposition is attractive to other developers, thus they're using it. It's not like they're forcing others at gunpoint to adopt their tech. If you don't want to use it, don't. Pick software that doesn't rely on systemd capabilities. Or advocate that that software gets written and maintained. Or write it yourself. Or stop complaining. Just don't tell somebody to not offer a capability.
- therealidiot 12y ago> If you don't want to use it, don't. Pick software that doesn't rely on systemd capabilities. Doesn't this becomes more difficult though, when things people are used to like KDE/Gnome are depending on systemd? What happens if more tools start depending on systemd? Will people just have to keep finding alternatives?
- Shish2k 12y ago> What happens if more tools start depending on systemd? Will people just have to keep finding alternatives? Linux becomes the new OSX (Slick, integrated, everything works great as long as you are doing the things that the system designers expect you to do); FreeBSD becomes the new Linux (Weird and confusing out of the box, but can be customised however you want it)