3 ms·
Philosophically I prefer the idea of "one tool for the job", and I don't like the idea that systemd has swallowed so many different services (from udev to dhcpd
by stevekemp 6y ago
Philosophically I prefer the idea of "one tool for the job", and I don't like the idea that systemd has swallowed so many different services (from udev to dhcpd).
But practically? It just works. It is consistent, very well documented, and I have to say that it has saved me a lot of time - writing systemd unit-files is almost a pleasure.
So, while I understand some people have very strong views, I'm kinda OK with systemd having "won".
Maybe in 20 years we'll have something different offered, and people will be hugging their systemd and refusing to move away from it?
- zozbot234 6y agosystemd is not even close to being "consistent" and "well-documented" enough to be all-around usable. It's not about people having "strong views" about it, it's about a bleeding-edge codebase with a very kludgy design being promoted for use in production systems.