3 ms·
What's funny is that some of these technical details are irrelevant now (some bugs have been fixed, some components decoupled etc.). But at that particular poin
by hdjjhhvvhga 5y ago
What's funny is that some of these technical details are irrelevant now (some bugs have been fixed, some components decoupled etc.). But at that particular point in time, you had a very strange situation where one crucial system component was being completely replaced by another without supporting both for an extended period of time. Normally it takes years like with Xorg and Wayland etc. Once the new kid on the block gets mature, everybody is switching anyway. All that drama was totally avoidable with some imagination.
- md8z 5y agoI don't really see how that's the case, systemd was always intentionally backwards compatible with sysvinit scripts. I'm not sure what other issues you're referring to but in most cases it seems one could probably just fall back to a shell script to implement a workaround like it would have been done previously anyway.
- hdjjhhvvhga 5y ago> I'm not sure what other issues you're referring to All hundreds of them. That was debated ad nauseam both here and on practically all Linux websites. See https://ihatesystemd.com/ https://ihatesystemd.com/ or https://nosystemd.org/ https://nosystemd.org/ for some examples.