2 ms·
I've been professionally maintaining large deployments (thousands of machines) using systemd for years now, as well running systemd on my Linux desktop for as l
by geofft 7y ago
I've been professionally maintaining large deployments (thousands of machines) using systemd for years now, as well running systemd on my Linux desktop for as long as upstream has defaulted to it, and I can't recall a single bug or a single negative business impact from tying too many features together. I recall on multiple times wanting to upgrade but I'm pretty sure it was always because I wanted fancy new features, not for a bug.
(That's not to say systemd has no bugs. I expect it does. We either just didn't run into them, or we tested whatever complex thing we wanted to do—far more than could be expressed in any other init system, process keeper, or systemd competitor—found it didn't work, and moved on. That would be indistinguishable from systemd intentionally not having some fancy feature, and it definitely didn't affect us in production.)
Meanwhile, I can remember numerous concrete bugs in the Linux kernel, concrete misfeatures, and downsides from having a monolithic kernel where if one thing goes south everything does. But nobody warns me to avoid Linux....