A package involving 69 individual binaries can hardly be called monolithic. Of course it can. If those binaries are tightly coupled (try replacing journald!),

A package involving 69 individual binaries can hardly be called monolithic. Of course it can. If those binaries are tightly coupled (try replacing journald!), then the whole set is monolithic. Myth: systemd is not modular. Not true at all. At compile time you have [...] Yes, like modularity is about selecting what to compile. Myth: systemd could be ported to other kernels if its maintainers just wanted to. [...] [...] look at the others you didn't pick, and the complexity of replacing them. And there it goes their argument about simplicity of systemd. How much different subsystems does an init system need? Myth: systemd doesn't allow your to replace its components. Not true, you can turn off and replace pretty much any part of systemd [...] OK, where's the spec so I could implement alternatives?