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 599048
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: A cople of comments.
by gilboa on Wed 5th Nov 2014 22:09 UTC in reply to "RE: A cople of comments."
Member since:

"People tend to forget that open source is not democracy but rather a meritocracy

The problem with this kind of argument on software is when two things start to happen at same time:
1) it get ubiquitous so most of people that need them have to conform;
2) the developers behind it keep pushing more tight integration/interdependency.

It make things very hard to replace as the cost to build alternatives become increasingly step. We have many examples on file formats, applications, and protocols to attest it, and as far as can see this is happening on systemd right now.

Even if I think systemd is, for now, a superior solution and even like the way it handle the system init steps, I really would prefer they drop the tight coupling. It would help if they were a bit more inclined to accept small compromises to their "vision". For example, I always hated the binary log from the start and thought that user-space firmware loading was a bad idea.

One thing not discussed is that Debian is very popular for servers, what is not the case for openSUSE, Arch, Fedora and other distributions. I guess, that reason alone explain why the echo chamber noise is way more powerful on it and why it is more a concern to the members in its trenches.

I don't doubt that maintaining a non-systemd based Linux will be increasingly impossible.
The reason for that are quite obvious:
* The old sysv + million of loosely coupled binaries was severely broken. (Hence the large number of projects that sought to replace it).
* At least to me, it seems that most of the developer community is happy to switch to systemd, leaving less capable people available to maintain a non-systemd fork on one hand, while creating a ever increasing gap on the other.

That goes back to the meritocracy: Unless the anti-systemd group manage to pull sufficient number of capable developers to lead the effort, its just a matter of time until all the major distributions fall in line - including Debian.

BTW, keep in mind that if you are old enough, things may change. XFree86 ruled the world for years, and vanished within a space of a year (replaced by once they got too arrogant.

- Gilboa

Reply Parent Score: 2