it's great making a product for linux users because they have such a low baseline expectation for things working out-of-the-box and will go to great lengths to help you debug
-
-
or slackware where nothing works for long, ever...but at least they don't use systemd
-
hahahahaha I understand the hate for systemd, but honestly is it really that bad seems like it offers a lot of flexibility.
-
yes it really is that bad. it takes the linux philosophy of doing one thing and doing it really well and turns it into doing everything poorly.
-
I get that it ruins the Linux philosophy of chaining together lots of smaller functional parts, but what is it specifically that people find so frustrating about it? It seems to me like it makes a few things easier at no real performance cost. I'm not a Linux admin though.
-
It makes all sorts of new failure modes possible and changes lots of behavior in incompatible ways.
-
The only thing it makes easier is shipping packages that automatically install themselves to start at boot, which distros like but competent deployment integrators/admins hate.
-
Thanks
@RichFelker. I'm not a Linux Admin, but use it a fair bit and my goal this year is to truly understand the differences between SysVInit and Systemd systems that have created such a clear point of contention among admins. I don't have the practical experience yet. -
I don't think anybody likes sysvinit. The false dichotomy was created by systemd pushers. There were literally at least 3 alternatives that had the advantages of systemd decades earlier.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.