The free software world needed an API for managing system resources. Poettering came along and provided one. It's not perfect, but it solved problems. The resistance to systemd isn't proposing alternative ways of solving these problems. It's instead insisting these problems remain unfixed. Is it any wonder that the anti-systemd camp has become irrelevant?
A lot of the resistance to systemd isn't resistance to the problems being solved, it's resistance to solving the problems with a big ball of interdependent components. As we saw in the xz attack, that's a huge attack surface to consider and the project's general hostility to producing small, focused libraries means that people often depend on it where they shouldn't.
i wouldn't mind the api where it must be different but all too often he had not invented here syndrom and reinvented things that worked great already while fixing what was broke. He also suffers from all the world is linux syndrom and so bsd needs to figure out how to solve the problem from scratch (mostly has not)
Worked great already? Like 3,000 line shell scripts parsing dependency information out of comments? That's what I mean when I say about insisting problems not be solved.
