Re:Write code that is easy to delete, not easy to extend (2016)
by mumblemumble on Wednesday July 22, 2020 @10:17PM
(#23923555)
Don't bring the Unix-Haters Handbook into this. A fun, self-consciously curmudgeonly romp like that has about as much in common with the systemd debate as P.J. O'Rourke does with Bill O'Reilly.
Re:Write code that is easy to delete, not easy to extend (2016)
by teddyh on Thursday July 23, 2020 @04:45AM
(#23925419)
I don’t know who any of those people are.
Re:Write code that is easy to delete, not easy to extend (2016)
by flohofwoe on Thursday July 23, 2020 @04:33AM
(#23925354)
I think the point of the parent was that systemd will be much harder to replace than other init mechanisms once something better comes along, because it grows into every part of a Linux setup. And if that's true, then systemd actually hinders progress and innovation, because the cost of replacement will be too high.
All software has problems. Without specific details, blaming your problem on systemd specifically seems just as unreasonable as blaming “Linux” or even “Unix”. In fact, in past years during the old OS wars, there were many such rants, blaming “Unix”. (See for instance The Unix-Haters Handbook.) Become a curmudgeon, and idolize the past, at your own peril.
I recommend, instead, to live in the present, to use currently normal software, and to fix every problem as it appears. Ceasing to upgrade permanently (possibly by moving to an obviously dead-end fork) is never a sensible option in the long run.