SoylentNews is people
SoylentNews
from the or-at-least-not-be-bothered-either-way dept.
[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 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.