4 ms·
This is especially true since any init system which sets out to "escape from systemd" will eventually end up doing everything that systemd does, at which point
by turbinerneiter 7y ago
This is especially true since any init system which sets out to "escape from systemd" will eventually end up doing everything that systemd does, at which point it will be as complex as systemd.
HOWEVER - the Linux world has lived with these problems for ages and I deem it also a strength. You can switch around components, mix and match and it will mostly work. You can run KDE apps on GNOME no problemo. I think this is something we should consider a positive. If we can unify around a common service file language, we can swap out service managers easy.
- jcelerier 7y ago> You can run KDE apps on GNOME no problemo. well you can also run KDE apps on windows and macOS so it would be quite the shit show if they did not run on GNOME :-)...
- turbinerneiter 7y agoThat's ... a good point.
- JdeBP 7y agoYou are basing your argument upon the false premise of doing everything that systemd does. Several people, perhaps most notably the Uselessd Guy, set out to do only a subset. After all, one of the common critiques is that one really does not have to reinvent things like a resolving proxy DNS server and an NTP server in order to manage services. (A resolving proxy DNS server is one of the things that is notoriously easy to reinvent badly, moreover. The DNS is full of traps for implementors.)
- co_dh 7y agoI hate things mostly work. Countless of hour of debugging, refactoring on the way. A system need to be designed first, proved correct first.