Wasn't Open/Free/whatever software about choice ?
I can understand that systemd brings some improvements.
In specific contexts.
For example, when your profession is sysadmin, when you have more than, let's say 4 or 5 servers to administrate, OK, may be systemd brings improvements over scripts. Real sysadmins are responsible of dozens, hundreds of servers.
What about other people like me ? I'm in computer programming since 1982, very well, but I'm no sysadmin.
A very kind friend told me once that, as a programmer, I'm a good sysadmin (I'm not sure I translated this properly from French), but I'm no sysadmin; first, I'm a programmer.
I mean that it's OK for me to have a Debian FW+many services at home, or to have one or two "shadow servers" at work to help me do my programmer job.
It's OK for me to install and configure services on a recent Debian, with systemd. As long as it's working. Magically.
What's not OK :
- few years ago, when Debian forced the change : it broke my system after an apt-get dist-upgrade. Before that, when a Debian had boot problems, I could handle them as long as I could dig in the scripts and trace the sequence. Suddenly, Debian replaced those scripts by systemd. At the first reboot, systemd was not pleased with something. The boot was interrupted with some cryptic error message, asking my to look at some logs, or run some new commands. What ? No ! No time, Internet connection broken, go to hell ! OK, I preferred to re-install a Debian from scratch, it was faster.
- this kind of problem still happens from time to time. Today, I'm afraid I still can not handle every situation. Most often : when a drive is missing, what will systemd do : a) timeout and continue ? b) timeout, put me in a shell that I can quit and continue ? c) timeout, put me in a shell, leaving me helpless because, with or without knowing what's wrong, I cannot (try to) correct the problem.
You could answer : RTFM.
Yes, but I have better things to do. I cannot read every man page of the world. And systemd manual is not small, and it needs practice. Reading alone is not enough.
So give me back the choice, give me back my scripts and let systemd to those who have time, or to those which profession it is to learn that monster !
And now that systemd has become a synonymous for Godwin point, let me ask : I've been told that systemd takes care of the network config by itself ? Or that it makes binary logs ? Seriously ? It cannot be, this is not the UN*X spirit, is it ?