> is that the author (Pottering or whatever?) fault?
Yes, he's got technically good ideas, but not a great experience with either security or large systems. He's also terrible at receiving critical feedback which makes this unlikely to change.
Some people chose systemd for the positive technical merits and others disagree. But just because his ideas got popular, it doesn't make him right and without blame for other behaviour. We have enough bad, popular leaders recently.
Ideally, I'd like systemd with each project split out with separate leadership and without Pottering. Nobody getting a pwnie award should be a leader of a large project.
I'd be curious to see what the Amazons, WalMarts & other large ''small service Linux-y thingy'' do to get so big & scale so fast: are they not essentially using CoreOS, many containers & making use of systemd to the fullest extent possible?
I just don't get it. Linux is all about choice (and yet nobody realizes too much choice is bad - just look at all the distros you have). Someone fixes it all for you & you get upset. Someone takes power away from Sysadmins & shifts it just a little more to Devs because they can't get work done. You get upset (I am admittedly in that camp) but, from the people that I hear good things about systemd, I hear great* things that convince me it's wonderful. The bad camp can't say the same thing on the same scale: it's just blame & resentment & frustration because they can't articulate what they don't like about it other than "It isn't the Linux way!!11Oneoneon1on1!! M$"