Systemd doesn't just replace 1000 lines of Sysvinit. Those "millions of lines" also replace the thousands of hundred-line poorly-vetted Bash scripts you need, plus your syslog daemon, plus dozens of "fork, setuid, chroot" variants, plus your cron daemon. And that's before we get into things not directly related to service management, like logind, hostnamed, networkd, resolved, timesyncd, tmpfiles, udevd, and so on.
Systemd is an umbrella project. Look at each individual component in isolation, and the vast majority of the time the thing it replaces is significantly more complex and fragile. Systemd was adopted by most of the Linux ecosystem because it was a significant improvement over the status quo, there is no need to invent conspiracy theories here.
[–] dv_dt 2 days ago
[–] preg_match 1 day ago
When people say systemd they really mean systemd-init, which is one piece of software. Not systemd-resolved, which is another.
[–] cowlevel 1 day ago
[–] preg_match 1 day ago
Most distributions only use some of them, and the “some” set is different from distro to distro. Many distros swap parts out. And some distros only use systemd-resolved.
Systemd is, legitimately, well divided. Most of the complaints against systemd are from people who know basically nothing about systemd.
[–] cowlevel 1 day ago
[–] preg_match 1 day ago
[–] cowlevel 1 day ago
How many pieces of software is nginx or Apache, where every feature is an optional plugin?
[–] gf000 22 hours ago
systemd-init has nothing to do with network resolution.
[–] cowlevel 21 hours ago
systemd-journald is a nicer example though.
[–] gf000 1 day ago