Firstly: I deliberately said supporters, not users.They are not the same thing. It very much is a choice, whether you want to call it political, that is up to you. I am a systemd user, I have it on my Fedora laptop, two Ubuntu servers and soon on one or two desktops, probably also Fedora or maybe Mint. That I use it does not make me a supporter or proponent. I use it for certain purposes. For other purposes on other machines, I do not use it and never would. Do not mix those two up. Most people who use UNIXoid systems professionally also have to use Windows machines at some point. That does not make them Microsoft supporters. Having a Dell monitor does not make me a Dell supporter.
Secondly: Your grand-standing about computer literacy is not exactly a sound counter-argument to what I wrote. Most system admins are incompetent (not as a judgement but literally lacking the technical competence to properly manage all aspects of running systems), I agree. To some extent I belong to them, I luckily do not run servers for a living, I can rely on others to do that for me. But people like me are not the benchmark here. People worth listening to do not complain about systemd in the belief that stuff never breaks. Quite to the contrary! Assuming breakage is the baseline from which you work up everything else. The issue I have with systemd is that it treats breakage as normal, working around it and trying to apply band-aids automagically. There are use cases for that, ie. the desktop (in most cases) and a certain portion of the server user base. But on my servers I do not want the system to route around damage unless I specifically set up fail safe mechanisms and fall backs myself. I want my machines to fail. So I know where trouble is brewing. And from my experience systemd has made it harder for me to debug issues. It is an opaque layer between me and the basic system functionality, and punching through has been more trouble and work than it should be. I like to compare it to NetworkManager: When that was introduced, it sucked. By now I love it on the desktop. On the server it is the first thing I purge from the system, because it has consistently caused problems and made things a lot more complex to set up and debug.
Thirdly: Do not confuse resistance to systemd with resistance to change. sysvinit has been showing its age for a long time. As have X11 and a few other parts of the ecosystem. I am happy to leave init scripts behind for a more sensible mechanism. But systemd is not the only kid in town. There are other initiatives to solve the issues we face, and most of them have taken a much less radical approach and far smaller scope. This is the way for me on the server side. This does not diminish the benefits some use cases draw from systemd right here and now. But it is not the holy grail some of its proponents make it out to be.