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.
Thread beginning with comment 599021
To view parent comment, click here.
To read all comments associated with this story, please click here.
Valhalla
Member since:
2006-01-24

I'm so happy that we have you to make decisions for every one else.

The people who do the actual work, as in making/providing the software, are indeed the ones who get to make the decisions for those who aren't.

There's nothing new here, if upstream chooses to take their software in a different directon than you want you can certainly ask them not to, but in the end the choice is theirs.

Your choice is to either step up and maintain a fork/patches which corresponds to your needs, or vote with your feet.

Reply Parent Score: 6

TemporalBeing Member since:
2007-08-22

"I'm so happy that we have you to make decisions for every one else.

The people who do the actual work, as in making/providing the software, are indeed the ones who get to make the decisions for those who aren't.
"

Actually in this case it's not even that. Most software in Linux doesn't depend on SystemD; only GNOME does.

Distros are switching because they want to support GNOME and the easiest path to do so is to switch the whole system over regardless of whether the user uses GNOME or not.

So, in the end, the decision of the GNOME folks to take a hard dependency on SystemD is screwing everyone else.

Reply Parent Score: 4

woegjiub Member since:
2008-11-25

KDE on Wayland is going to have a dependency on the logind interface too, btw.

I think it's a "tip of the iceberg" scenario.

For now, it's Gnome and KDE. What's next?

Of course, you'll always be able to run your favourite TWM on X on BSD, so if you're the kind of person that gnashes their teeth about losing init scripts, you'd probably be more comfortable there.

Reply Parent Score: 3

Finalzone Member since:
2005-07-06

Actually in this case it's not even that. Most software in Linux doesn't depend on SystemD; only GNOME does.

Distros are switching because they want to support GNOME and the easiest path to do so is to switch the whole system over regardless of whether the user uses GNOME or not.

So, in the end, the decision of the GNOME folks to take a hard dependency on SystemD is screwing everyone else.

Need to remind nobody stepped up to maintain ConsoleKit despite GNOME warning for years. GNOME uses logind and KDE recently adopted it. Those are a few example where most non systemd people only talk but do nothing.

Edited 2014-11-06 22:26 UTC

Reply Parent Score: 3