It replicates a lot of unix tooling poorly, binds the to the Systemd framework and only runs on Linux. So, still a monolith.
Systemd isn’t monolithic, it’s a pluggable framework with a shit load of components
MonkderVierte@lemmy.zip 3 weeks ago
imsufferableninja@sh.itjust.works 3 weeks ago
That’s … not what monolithic means, in software architecture
greyscale@lemmy.grey.ooo 3 weeks ago
ok so tell me why I’m waiting for networking to come up before I’m allowed to interact with my computer
Also, its monolithic as heck, its a giant squid into my networking, time management, access control…
Ontop of that… binary logs ew.
Natanox@discuss.tchncs.de 3 weeks ago
Because your distro sets up stuff weirdly? At least I never noticed networkd to be a dependency of multi-user.target, could be wrong though.
That’s all optional though, many distros just use it because it’s easier than the alternatives.
Yeah, that’s indeed stupid. No clue why they did that.
imsufferableninja@sh.itjust.works 3 weeks ago
Pervasive, yes. Deeply embedded in the district that is it, absolutely. And I get why people don’t like binary logs, although that isn’t exactly relevant to monolithic vs pluggable.
You seem to think that I’m arguing against your opinion that systemd is bad. I’m not. I’m arguing against the false statement that it is monolithic. It isn’t. It’s modular, like the linux kernel. If you wanted to remove every component except the init system, you could. Big pain in the ass to do that, but you could.