> They don't have the push to constantly changing stuff around for the sake of things like systemd and net-tools. I assume you forgot a word here and intended

> They don't have the push to constantly changing stuff around for the sake of things like systemd and net-tools. I assume you forgot a word here and intended to write "changing stuff around for the sake of changing things"? I just want to set the record straight: systemd solves the startup-dependency problem. Yes the old default init scripts worked fine for your system (that probably had very few services installed other than vanilla defaults), but it was insufficient for handling the exploding cascade of dependencies when service1 depends on the network, service2 depends on the graphical subsystem, service3 (the wifi daemon) can restart the network, etc. People tried in vain, hacked nasty rc.init scripts for years, until Poettering took matters into his own hands. I will stop there because I dont know the whole history behind it, but I just take issue with the attitude that systemd in particular is just kids messing around with the latest-new-thing. Some of that does exist in the Linux sphere, even worse, with some maintainers putting inappropriate images and political messages in their apps[1]. But systemd - as with wayland - solves a problem that had been brewing a long time.I suppose you could almost think of it as a fix for developers instead of end users? I'm not compelling you to use it, just disputing your final point. [1]. https://www.reddit.com/r/browsers/comments/18izmt4/clarifying_thorium_browser_controversy/ https://www.reddit.com/r/browsers/comments/18izmt4/clarifyin...