What is this? Some crazy guy makes significant changes to a standard, the distribution maintainers will just gobble it up (as per usual) and then I have to weigh the pros and cons instead of complaining and fixing/adapting my systems e.g. wasting time because of a crazy guy's ideas?
There is no market in OSS. It's either use it or leave it. But even in OSS there are established standards which are relied upon! Poettering doesn't care about that, because he likes change.
Now what were those problems, specifically, for distros, that weren't caused by systemd eating and replacing previous solutions, which suddenly became unmaintained and unsupported?
(I'm looking especially at udev and all the dbus hookery.)
You missed out the step where the knowledgeable people who run and have to support most of the major distros adopted systemd. When's that going to backfire? Any day now, right?
I don't understand your last paragraph. Did the guy behind systemd use OSS or leave it?
What is this? Some crazy guy makes significant changes to a standard, the distribution maintainers will just gobble it up (as per usual) and then I have to weigh the pros and cons instead of complaining and fixing/adapting my systems e.g. wasting time because of a crazy guy's ideas?
There is no market in OSS. It's either use it or leave it. But even in OSS there are established standards which are relied upon! Poettering doesn't care about that, because he likes change.