Frequently Asked Question

Why is systemd controversial?

The objections fall into a few overlapping camps. Critics point to scope creep: systemd began as an init system but absorbed logging, network configuration, DNS, time synchronisation, login management, device hot-plug, and bootloader work, which they see as violating the Unix philosophy of small composable tools. Others worry about single points of failure (everything depends on one daemon family) and portability (systemd relies on Linux-specific kernel features and so cannot be ported to the BSDs). The binary journal and the personalities involved in early adoption debates also added heat to the discussion.

Defenders answer that the responsibilities of an init system have legitimately grown, that the older separate tools had accumulated baroque interfaces and bugs that were easier to fix by rewriting them together, and that systemd's declarative units, dependency-aware parallel boot, and integrated supervision are real engineering improvements over what came before. Debian held a formal vote in 2014 and chose systemd; by around 2020 essentially every major distribution had adopted it. Devuan, Artix, Alpine, and Void remain available for those who prefer alternatives, but for most Linux users systemd is now simply the init system.