Linked by jessesmith on Wed 5th Nov 2014 10:39 UTC
Linux Over the past year I've been reading a lot of opinions on the new init technology, systemd. Some people think systemd is wonderful, the bee's knees. Others claim that systemd is broken by design. Some see systemd as a unifying force, a way to unite the majority of the Linux distributions. Others see systemd as a growing blob that is slowly becoming an overly large portion of the operating system. One thing that has surprised me a little is just how much people care about systemd, whether their opinion of the technology is good or bad. People in favour faithfully (and sometimes falsely) make wonderful claims about what systemd is and what it can supposedly do. Opponents claim systemd will divide the Linux community and drive many technical users to other operating systems. There is a lot of hype and surprisingly few people presenting facts.
Permalink for comment 598983
To read all comments associated with this story, please click here.
Member since:

That's the point though: If you don't like software depending on systemd, it's up to you to fork the software, because clearly the people who actually write it aren't interested in sysvinit compatibility.

That's why we have eudev, uselessd, and consolekit.
They all have serious downsides, but at least the devs are putting their money where their mouths are, and writing alternatives.

tl;dr: Software becomes dependent on systemd. Choices:
a) Fork sotftware
b) Use systemd

Reply Parent Score: 4