3 ms·
> What you're not understanding is that when we describe something as "monolithic" (or "modular") we're talking about if the design[2], not the number of binari
by Ao7bei3s 11y ago
> What you're not understanding is that when we describe something as "monolithic" (or "modular") we're talking about if the design[2], not the number of binaries it happens to compile into.
What you're not understanding is that these other binaries do not run as PID 1, which is what nextos wrongly claimed.
> This is about minimizing complexity, and the way to do that is to break the problem into small pieces, while clearly and rigorously defining the interconnections between those pieces (an area that necessarily involves higher complexity).
Which is the exact opposite of what has happened during the sysvinit times.
- pdkl95 11y ago> other binaries do not run as PID 1, which is what nextos wrongly claimed. I never claimed they did. Obviously, I was replying to this claim: "Systemd is not a monolith, it is a bunch of various utilities." > Which is the exact opposite of what has happened during the sysvinit times. I never mentioned anything about sysvinit, which has nothing to do with the bad design in systemd. Regarding those times, I would agree that the older sysv-rc/initscripts were not that great either, which is why many of us moved to OpenRC a long time ago.