There is no reason the creation of privileged sessions should depend on a particular init system. It's fairly obvious that is a bad idea from a software design perspective. The only architectural reason to build it like that is because so many distros already include systemd, so they don't have to worry about getting people to adopt this (incidentally, that's the same reason Microsoft tried to deeply embed the browser in their OS.....remember active desktop?)
Poettering is following the philosophy that has created nearly every piece of bloated software that is in existence today: the design is not complete unless there is nothing more than can be added. Bloated software feeds upon the constant influx of new features, regardless of whether those new features are appropriate or not. They are new therefore they are justified.
. You know you have achieved perfection in design, not when you have nothing more to add, but when you have nothing more to take away. -- Antoine de Saint-Exupery
quality engineering (Score:4, Insightful)
If there are any systemd fans out there, I woul
Re:quality engineering (Score:5, Insightful)
.
You know you have achieved perfection in design, not when you have nothing more to add, but when you have nothing more to take away.
-- Antoine de Saint-Exupery
Re: (Score:2)
You know you have achieved perfection in design, not when you have nothing more to add, but when you have nothing more to take away.
-- Antoine de Saint-Exupery
Love that quote.
Re: (Score:2)
I think he knows the quote but misunderstands it.
You know when SystemD has achieved perfection in design when there is nothing to take away from the rest of the system.