Another daemon for managing control groups

> For example, in the traditional setup there are four or five different ways of starting background service processes, all configured differently, most not really working properly, and none aware of each other – mostly through a series of accidents of history. With respect, this is not how one constructs »high quality software«. I wonder how people can claim, with a straight face, that doing things this way is a Good Idea

I remember reading about an experiment with monkeys in a cage. There was a banana hanging from the ceiling but when any of the monkeys tried to reach for it, all of them were sprinkled with cold water. Avoiding the cold shower was more important than getting a banana, so soon whenever one monkey tried to reach for the banana, other monkeys prevented it. Over time the monkeys were being replaced one by one and each time the newcomer would try to reach for the banana and would be violently suppressed by others. And this persisted even when there were no monkeys left that experienced the cold shower. The banana became "taboo". This is how tradition emerges.

I think of this story each time I read someone passionately defending the "Unix Way" and using it against systemd...