This reminds me of the early days of "web services." The "enterprise" folks were jetting around writing gobs of XML and SOAP specifications, making speeches at conferences and whatnot. Meanwhile, some thoughtful people pointed out that the combination of existing HTTP verbs and the natural namespace provided by URLs satisfied the same use cases without the mountains of esoteric specifications and staggering protocol overhead. One memory I have from that time has persisted; some SOAP standards body muckity-muck was asked about REST during some function that happened around the time of the SOAP 1.0 specification release and he said (paraphrased); "Those REST folks aren't the kind of people the get things done!"
Today, SOAP gives people nausea almost universally and REST is the first choice of green-field work, with all sorts of API's proliferating everywhere. New languages and tools target REST first and SOAP eventually. Maybe. And if not then, meh, whatever.
Now we have the Debian fork. And what is said of the people behind it by those advocating systemd bloatware? Well they're just malcontents. They don't understand the problem systemd is trying to solve. They made a crummy web site and didn't even put their names on it. They'll never accomplish anything!
I have the feeling Poettering et. al are going to lose this one. If so then at least we can credit systemd with providing the motivation to progress, and reaffirming some of those cherished (if possibly mythical) UNIX principles.
(Incidentally, if anyone knows who was responsible for that statement about REST I mentioned please chime in .... I'm 99% sure it appeared on Slashdot.)