If we're going to do block quotes... I refer you to http://0pointer.de/blog/projects/the-biggest-myths.html
, in which it is clearly stated:
Myth: systemd is monolithic.
If you build systemd with all configuration options enabled you will build 69 individual binaries. These binaries all serve different tasks, and are neatly separated for a number of reasons. For example, we designed systemd with security in mind, hence most daemons run at minimal privileges (using kernel capabilities, for example) and are responsible for very specific tasks only, to minimize their security surface and impact. Also, systemd parallelizes the boot more than any prior solution. This parallization happens by running more processes in parallel. Thus it is essential that systemd is nicely split up into many binaries and thus processes. In fact, many of these binaries are separated out so nicely, that they are very useful outside of systemd, too.
A package involving 69 individual binaries can hardly be called monolithic. What is different from prior solutions however, is that we ship more components in a single tarball, and maintain them upstream in a single repository with a unified release cycle.
systemd is already "a collection of small programs, each tackling one specific, well-defined component of the larger task", so I don't see what the issue is.
Please take some time to actually research the facts instead of reiterating FUD that's already been debunked. This bug is long enough.