Comment This Is How It Starts (Score 4, Insightful) 104
First it's KDE's login manager. Next, it will be some other portion of KDE due to another dependency, maybe systemd-homed. And other projects are almost certain to follow. This is Red Hat's version of embrace, extend, extinguish (which is likely a big reason why IBM bought Red Hat). They keep making additional modules that are exclusive to SystemD with enticing functionality, they lure downstream projects to integrate those modules, and before you know it the dependencies are so intertwined with this exclusive functionality that the downstream project can no longer support any other init system. Say what you want about all of the other init systems available, but I can't think of another init system that pulled shit like this. They didn't have to implement SystemD like this, but they chose to because it allowed them to exert undue influence on many other downstream projects (and when you're an init system, almost every component is a downstream project). If you like SystemD, fine, but let's not pretend this outcome is incidental, let alone healthy for alternative init systems.