This is a really stupid.
Quite a blunt reply. I stand by what I said about 'the average user'.
The choice of the right OS should begin with how are the developers.
Perhaps it should. But does that mean it does? Go out and ask 20 people on the street who develops their operating system and report the answers back here.
Even if they
can pronounce Volkerding do you honestly believe they know what motivates him? C'mon, who's being stupid? Do you give the same importance to the computer that runs your OS? Do you wonder about the motivation of Toshiba or DELL and why they introduced secure boot? Porbably not. It boots your OS, which gets you into an environment to accomplish your computing goals.
Who has the largest percentage of users in the computer world? <-- obvious
Do you think they even know what version of OS they are running? <-- many think their OS is microsoft office
Why do they use the computer in the first place? <-- 95% will say to use the internet or office apps
As an example I put Porteus on a thin client at my work. Nobody even noticed the difference for 3 months. Then someone realized that it was faster and didn't crash. They had absolutely no idea what OS they were using and didn't really care, as long as it got the job done. That is where my comment came from. Notice I separated 'average users' from 'power users'. Power users fall into another category. The category that come and use Porteus or that stray into the world of Linux in general.
Why is development always for the non power users?
It's not. Look at Arch Linux, Gentoo, BSD, LFS, Slackware etc.
For example it is not good when the distrubition depends only on one Man.
Hey, feel free to help out any time. It would be much appreciated.
Is that right that Arch a team with 25 people?
I don't know, but they do an awesome job. Best wikis on the planet in my opinion. We can make use of that.
What is there propulsion?
See my answer above.
@ Tonio
People have made comments specifically about the size of systemd. Some don't believe that it can even be used as a 'portable lightweight' solution. It can be intrusive (I doubt NSA plant type intrusive since the code is rather open) but there is always the option to disable the parts you don't want. I am happy for it to take over journaling (although binary journals suck) and even cron jobs as it unifies the problem and takes away worrying about any dependencies. I think creating slackware live scripts to build Porteus can be done, but it is not as simple as that. There is initrd.xz, 000-kernel and vmlinuz to maintain.
Perhaps when systemBSD matures a little it can be used in place of systemd.