The unix philosophy is that a piece of software should do one thing, and do it well. Systemd does a dozen things, all of them poorly. It’s an especially poor choice for an embedded or appliance system.
Linux is a kernel. The kernel modules, services, userland, etc. are all modular and can be used independently. Not so with systemd (at least how it’s implemented in most distros).
I’m sure there’s several modules in the Linux kernel that are necessary to function, and you’re also aware that when people broadly refer to Linux, they don’t mean the kernel specifically lol
The unix philosophy is that a piece of software should do one thing, and do it well. Systemd does a dozen things, all of them poorly. It’s an especially poor choice for an embedded or appliance system.
Systemd is not a singular thing, it’s a collection of a lot of things.
Yes, that’s the problem.
Linux is not a singular thing, it’s a collection of a lot of things.
Linux is a kernel. The kernel modules, services, userland, etc. are all modular and can be used independently. Not so with systemd (at least how it’s implemented in most distros).
I’m sure there’s several modules in the Linux kernel that are necessary to function, and you’re also aware that when people broadly refer to Linux, they don’t mean the kernel specifically lol
I don’t see the problem but I was just saying that it doesn’t break the unix philosophy as such. Not that unix philosophy is much of a thing anymore.