4 ms·
Copying my reply from Lobste.rs because there’s more people here who can pick me apart: _FD: I’m not a large supporter of SystemD after using it when it was fi
by dijit 6y ago
Copying my reply from Lobste.rs because there’s more people here who can pick me apart:
_FD: I’m not a large supporter of SystemD after using it when it was first introduced in Fedora and watching it take over the ecosystem, I do use it and as a sysadmin/SRE type I’m heavily versed in it and how it functions, so, everything with a pinch of salt._
I gave the video a good shot, half the time is spent going over some systemd-ecosystem basics;
The author then makes the case that Alpine is a less attractive development/production-deployment platform due to lack of this ecosystem (though they make effort to avoid directly saying that systemd would be a good solution itself.)
I couldn’t disagree more honestly. I love the concept of Alpine: as small as possible and no smaller.
The attention to minimise dependencies makes it the distro of choice in containers; I’ve even considered (strongly) running it on some machines where systemd would have been a lot of needless complexity.
I think deviating from this path for alpine is a grave error, there will always be a place for a niche system that is small; especially when it’s commonly paired with some other log managment/service orchestrator like Alpine is.
Additionally, it gives people like me an option to run without init systems that could be considered heavy and intrusive with heavy dependency chains.
So, kindly, Alpine: please don’t.