# systemd 326 Hacker News commenters recommended systemd and 335 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months; owners who said how long report a median of 14 years (8 owners). **Verdict:** Praised as a solid Linux service manager with declarative unit files, sandboxing and consistent standardization, though critics dislike how much it absorbs beyond init and its tight coupling. ## Why people recommend it - Solid init and service manager (5 comments): "While I think systemd is a great init system (as well as some other components under the systemd umbrella), I really dislike when components up in the stack hard-depend on it." ([source](https://news.ycombinator.com/item?id=48277684)) "I find systemd pleasant for scheduling and running services but enraging in how much it has taken over every other thing in an IMO subpar way." ([source](https://news.ycombinator.com/item?id=46576393)) "SystemD as init replacement is "fine"; SystemD as kitchen-sink-of-the-server-with-everything-tightly-coupled can get annoying." ([source](https://news.ycombinator.com/item?id=46321807)) - Declarative files replace shell scripts (3 comments): "I've heard from many sysadmins and distribution maintainers that systemd has been amazing. We went from ad hoc shell scripts to declarative plain text files." ([source](https://news.ycombinator.com/item?id=47152805)) "The whole philosophy of systemd is to move away from these kinds of "simple" and "mostly working" pile-of-shell-script systems" ([source](https://news.ycombinator.com/item?id=46880125)) "With systemd that all becomes explicit, so of course it is awkwardly verbose. That is the whole point and a huge upgrade." ([source](https://news.ycombinator.com/item?id=49057522)) - Modular, well-divided components (4 comments): "Systemd is not 1 giant thing that does 100000 things - it is a collection or 10000 services doing 10000 things, integrating amongst themselves where practical." ([source](https://news.ycombinator.com/item?id=49058129)) "Systemd is, legitimately, well divided. Most of the complaints against systemd are from people who know basically nothing about systemd." ([source](https://news.ycombinator.com/item?id=50282085)) "systemd is 69 different binaries (only one of which runs as pid 1), all developed under the same project, designed to work together" ([source](https://news.ycombinator.com/item?id=46107888)) - Easy process hardening and sandboxing (4 comments): "systemd makes it so so easy, and integrates many many different mechanisms and systems for locking down what procesess can do" ([source](https://news.ycombinator.com/item?id=49770436)) "The hardening options highly restrict the unit files from accessing anything more than it's required for it's function." ([source](https://news.ycombinator.com/item?id=45952987)) "A lot of the things make image based systems more modifiable/user accessible without compromising on the general security aspect." ([source](https://news.ycombinator.com/item?id=47524839)) ## What people warn about - Takes over too much beyond init (5 comments): "While I think systemd is a great init system (as well as some other components under the systemd umbrella), I really dislike when components up in the stack hard-depend on it." ([source](https://news.ycombinator.com/item?id=48277684)) "The problem with systemd is not the init system. Most people who do not like systemd are happy with the init system, but do not want the rest of it." ([source](https://news.ycombinator.com/item?id=49069560)) "systemd and friends go around absorbing other projects by (poorly) implementing a replacement and then convincing the official project to give up." ([source](https://news.ycombinator.com/item?id=46579492)) - Monolithic, tightly coupled stack (4 comments): "systemd also took a relatively non-unixy approach, where it's a big stack to adopt, rather than individual programs that work together well" ([source](https://news.ycombinator.com/item?id=46794340)) "SystemD is not "building blocks" — which implies modularity — it is a monolith: components cannot be added or taken away or replaced." ([source](https://news.ycombinator.com/item?id=49761712)) "With systemd, core updates can affect PID 1, logind, journald, udev, user managers, socket activation and cgroup state as one dependency graph." ([source](https://news.ycombinator.com/item?id=49124726)) - Complex and poorly documented (4 comments): "systemd is awfully documented (volume is not quality), things are still changing and haven't even caught up in functionality with any init hack." ([source](https://news.ycombinator.com/item?id=49060305)) "many options that are complicated beyond the understanding of the distro maintainers, and yet still don't allow expression of common semantics" ([source](https://news.ycombinator.com/item?id=46787949)) "SystemD has a lot more people refining it down but a clean (under the hood) implementation probably won't be witnessed in my lifetime" ([source](https://news.ycombinator.com/item?id=46786964)) - Disruptive bugs and behavior changes (4 comments): "...and then keep up with behavioral changes that the Systemd Project people introduce and load-bearing bugs that services end up relying on for lifecycle management." ([source](https://news.ycombinator.com/item?id=48717909)) "systemd doing dumb shit device naming so that changing the physical location of an unrelated GPU renames your NIC and breaks your internet" ([source](https://news.ycombinator.com/item?id=46481055)) "Why the fuck does systemd lock up the entire startup process for 2 minutes if you start a desktop machine without network connectivity?" ([source](https://news.ycombinator.com/item?id=46324167)) ## Alternatives hackers recommend - [daemontools](https://hackerapproved.com/p/daemontools.md): 9 recommend - [launchd](https://hackerapproved.com/p/launchd.md): 6 recommend ## Cite as Hacker Approved, "systemd", https://hackerapproved.com/p/systemd/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).