Replacing Systemd with OpenRC in Debian
A user discusses their discomfort with the systemd init system in Linux, citing its expanding scope and integration of non-essential features. The author expresses concern over the project's tendency to take on responsibilities beyond its original purpose as a PID 1 process.
Why it matters
It highlights the ongoing debate within the open-source community regarding software modularity versus monolithic integration.
TL;DR I'm not a fan of systemd but I'm not against its use either. AKA if it works for you then it's ok. My case though is more of a mix between curiosity and discomfort . Curiosity of how init systems works and discomfort of how systemd integrates things or new features.I'm aware that it works well for most of its use cases (I've been using it since its early days) and also I agree that systemd breaks all KISS philosphy principles, but other projects do it as well, right? So why the discomfort? Well it began a while ago, when I was reading some news of how the project started to grab more and more responsibilities that belongs to other projects and how some prod deployments failed so bad because of a breaking change that could've been prevented if that responsibility wasn't part of systemd . Nothing too worrying for me though, in any case the first real kick of discomfort came when
The article presents a personal opinion on software architecture without political or partisan framing.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in