[Ed's Comment: Not wishing to ignite yet another flame war regarding the adoption of systemd, I hesitated before publishing this story. However, although it is not an formal survey, it might still reflect the views of the greater linux user community rather than those who frequent this particular site. There is no need to restate the arguments seen over the last few weeks - they are well known and understood - but the survey might have a point.]
http://q5sys.sh has recenlty conducted a survey finding many Linux users may be in favour of systemd:
First off lets keep one thing in mind, this was not a professional survey. As such the results need to be taken as nothing more than the opinions of the 4755 individuals who responded. While the survey responses show that 47% of the respondents are in favor of systemd, that does not mean that 47% of the overall linux community is in favor of systemd. The actual value may be higher or lower. This is simply a small capture of our overall community.
Although the author questions the results could this be an indication that we're really seeing a vocal minority who don't want systemd while the silent majority either do or simply don't care? Poll results and the original blog post.
(Score: 3, Insightful) by emg on Thursday November 20 2014, @09:42PM
How many of the people polled actually know enough about init systems for their opinion to matter?
If you'd asked people about Pulseaudio, I'm sure most would have been in favour of its unicorn and rainbows solution to Linux's sucky audio... but, a few months later, they were posting on the Internet asking how to get rid of it because it was such a disaster for several years afterwards.
(Score: 3, Insightful) by frojack on Thursday November 20 2014, @10:20PM
If your computer boots, you are usually satisfied.
If you can get your work done, you're probably ok with it.
If it improves your life, things run faster, its more secure, easier to understand, goes less berserk, you are a happy camper.
So far, NONE of the promises have been fulfilled. Nobody's life is easier due to systemd.
But by the same token, none of the disasters that was pulseaudio have shown up either. Just a steep learning curve for zero benefit.
People new to linux will just learn it like we learned sysvinit, and they will know nothing different.
No, you are mistaken. I've always had this sig.
(Score: 1) by fritsd on Thursday November 20 2014, @10:46PM
"If your computer boots, you are usually satisfied."
Maybe it's my pessimistic outlook, but I have a related but quite different requirement as well:
"If my or my customer's computer *doesn't* boot, and I can debug and fix it, I am usually satisfied"
System administration is easy as long as everything goes to plan. It's when it all goes foobar that you need your toolkit to fix it. And that is when system complexity bites you.
(Actually, that seems to match your expression "easier to understand")
(Score: 2) by maxwell demon on Thursday November 20 2014, @11:53PM
If you can fix it, it does boot (it it still doesn't boot you haven't fixed it). Assuming your satisfaction only comes after having fixed it, not after finding that it doesn't boot, the line "if your computer boots, you are usually satisfied" applies to you. It's just that for you, usually the computer boots because you managed to fix it after it initially didn't boot.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2, Informative) by Anonymous Coward on Thursday November 20 2014, @10:50PM
There have been disasters. I had it happen to my Debian system. Systemd got installed, and it no longer booted properly. While searching for solutions, I ran across a lot of Debian bug reports and mailing list postings describing similar disasters affecting other people.
Now my Debian system doesn't boot at all. That's because I replaced it with FreeBSD after this ordeal, rather than trying to fix it. It's the best decision I've made in a long time. I'm done with Linux.
(Score: 1, Troll) by quixote on Friday November 21 2014, @01:32AM
to have an informed opinion on systemd. I'm pretty sure I'm using it (Debian jessie/testing), and did notice that boot times suddenly went down by about 10x when (I think) it was implemented.
Does that mean I'm for it, for some unspecified value of $for? Well, I don't like what I hear about it making the init process more opaque, about it maybe having some kind of roots in Redhat wanting to push us all into clouds, about Poettering of pulseaudio being some kind of central to it. So, yeah, it makes me nervous.
But there's another factor that's actually moving me toward giving it the benefit of the doubt: The devs who do seem to know something about it respond politely to doubters and even try to explain what's going on. And -- the biggest factor -- the anti-systemd-ers who slag off supporters as "social justice warriors," scream like wounded banshees, and even issue death threats.
Enough already. I just wanted to let the screamers know that you've lost one potential vote by what you're doing.
(Score: 0) by Anonymous Coward on Friday November 21 2014, @08:06AM
social justice warriors
hipsters
{insert others here}
Whenever you encounter the “label of badness” of the day you can safely stop reading.
(Score: 0) by Anonymous Coward on Friday November 21 2014, @12:22PM
It's a blanket term now. "You'll take it and like it", attitudes.
Ironically similar to the windows 8 interface and the user response.
We all know how that turned out.
(Score: 2) by choose another one on Friday November 21 2014, @01:42PM
How many of the people polled actually know enough about init systems for their opinion to matter?
Ah yes, the fallacy of the democracy - we count everyone's vote as equal whatever their level of knowledge and intelligence, which allows us to conclude that any vote is wrong because the voters were stupid (oddly, this is a more typical conclusion of those who lost the vote than those who won it...).
Question is, how would you decide who "knows enough" to vote ? Would it per chance have anything to do with agreeing with your opinions ?