Comment Re:So what's wrong with systemd, really? (Score 2) 385
Binding previously-separate features into one project is bad design, by itself, the problem with systemd.
Why? Justify that statement without using any reference to the UNIX way or it being the way things have always been designed.
IMHO a coordinated set of functions that are used in a common way should be combined. Why is it that to parse a log file I need to run grep, and sed, and all these other utilities in a continuous pipe? For that matter why should the tail command be able to open a file, is that against the unix way because everything should be grepped into it?
I'm getting sick of using 1000 different utilities to do one task or manage one system. Hate me, down mod me, argue with me, but I for one am a big fan of big software with multiple functions approach. If that one program does it well why wouldn't you let it manage multiple coherent tasks like getting a computer from nothing to at least a login prompt?