back
1 comments
Just don’t want it forced on me and by its nature it becomes a hard dependency over time, thus, it does.

I’m not interested in another argument but calling my position “pitchforks” is a bit disengenuous and irritating (which is why I’m replying, off-topic, to you).

While I think it has something to offer I would like potentially better alternatives to be able to exist in future, this is not “pitchforks”.

>Just don’t want it forced on me and by its nature it becomes a hard dependency over time, thus, it does.

systemd is the choice of basically everyone who builds distros, so of course it's going to be hard to avoid unless you volunteer to do all of that work yourself. When you take work from someone else, that comes with taking on the choices that they make.

Don’t let this descend into another systemd thread. Just don’t lump all criticism against systemd as pitchforks, since it delegitimises complaints.

What you state is absolutely true, but denying there’s more nuance is not helpful. That’s all I’ll say because this is not a worthwhile conversation to have here.

> systemd is the choice of basically everyone who builds distros

Even if we ignore the fact that systemd made it artificially difficult* for distros to support other init systems (so it wasn't a freely made "choice"), have you never encountered a situation where the popular choice turned out to be the wrong one? Think, for example, of people throwing their trash into nearby rivers, or developers using 2 digits to store year values.

(* Imagine being a volunteer for a distro and having to deal with bugs like "I installed my new printer and it changed my init system[0] / my system no longer boots").

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863974