I think it is breaking the Unix philosophy, it is an enormous piece of code that does so many different things. My ideal is smaller components with smaller dependencies. When distros or software becomes inextricably dependent on systemd they are then beholden to whichever direction the maintainers take it.
My take on it is somewhat based on “what if.” Other people have some pragmatic discussions on security aspects if you search around.
I’m not a systemd guru, but I do find it relatively easy to work with.
I’ve noticed that a lot of it is actually made up of separate binaries and daemons. Is it wrong or misleading to think of systemd as a collection of utilities that share a common DSL as opposed to a strict monolith?
I think it is breaking the Unix philosophy, it is an enormous piece of code that does so many different things. My ideal is smaller components with smaller dependencies. When distros or software becomes inextricably dependent on systemd they are then beholden to whichever direction the maintainers take it.
My take on it is somewhat based on “what if.” Other people have some pragmatic discussions on security aspects if you search around.
I’m not a systemd guru, but I do find it relatively easy to work with.
I’ve noticed that a lot of it is actually made up of separate binaries and daemons. Is it wrong or misleading to think of systemd as a collection of utilities that share a common DSL as opposed to a strict monolith?