What are the objective disadvantages of systemd?

Question

linux

Why is the "community" so "burned" by systemd? Where does this hatred and "buhurt" come from? What are its objective shortcomings?

Answer 1

Usually systemd haters are 14-18 years old and have never seen real Unix™.
1. systemd is the best thing that has happened to the init system of GNU/Linux distributions in the last 18
years times in certified Unix™ live.
And all these squeals about “not Unixvein” are heard from those who only read from their mother’s computers on Laura that it’s necessary to squeak like that.
Quote taken from here:
https://habr.com/ru/company/southbridge/blog/31570...
I agree with the author 100%.

Answer 2

It is interesting to see how right now Haters in the Yandex clickhouse are making a bicycle on init + sed to simulate 1 line Restart :)
Just think about what is happening. I started the service, a task was added to the crown, if the service has fallen, start it. If the service is stopped by a script, the cron task is removed. There are no words, only emotions. Are you worried about some kind of glibc, where the package in their dependencies does not pull which, but uses s in scripts? Familiar huh? Yes, pray for systemd, finally put things in order in this disgrace of all sorts of upstart, SysV, udev and a bunch of other goodness! And who else didn’t know, but my love warmed up a fart, when garbage or inaccessible nfs is written in fstab, the server does not turn on at all! And you need to mentally spend time like that, well, if there is ipmi, then the question is 5 minutes, but if not? So that's what I'm talking about, there are .mount units, the same kaef + dependency was thrown so that the service without balls does not take off and fall after the ball. The server will start, there is no ball, the service will not rise either, and you can log in via ssh and, most importantly, fix it easily and quickly. And this is only a small part of the pain that systemd really solves right now without dancing and blood from the eyes.

Answer 3

Actually sytemd was a step forward and got rid of the zoo of any kind of scripts in /etc/init.d/ but:
1 everyone remembers how it was planted and how pulseaudio works "well"
2 the sudden implementation of systemd brought a lot of confusion and related problems.
Package maintainers still sometimes fail to write the correct unit file that arrives on the production server and causes inconvenience (especially parameters such as ProtectSystem=full) but this is of course the case with package maintainers and not systemd
. Compared to the old system, init scripts have no drawbacks.

Answer 4

I regret that without understanding, I put a server with systemd in production. In three months, I collected as many problems as there were none in three years on sysVinit. And for the desktop, the benefits are dubious. Especially when the root FS starts to crumble, and he is not able to fschk on it ...