<i>No more problems with overflowing logfiles</i><p>Not quite. The journal is prone to fragmentation, though it can be capped just as most sane loggers like multilog can.<p><i>no more debugging undocumented shell scripts for booting</i><p><i>no more writing init scripts</i><p><i>no more debugging undocumented 200+ line init scripts</i><p>Redundant complaints, and irrelevant. Not all script-based init systems are created equal, and many init systems throughout history have eschewed shell scripts [1].<p><i>no more minute-long boot delays</i><p>Incorrect. Boots can still stall from dependency loops, cyclical transactions, stuck start&#x2F;stop jobs, an improperly calculated service ordering in the parallel dependency graph, etc.<p><i>no more brittle, half-assed distribution-specific networking solutions (also undocumented shell scripts)</i><p>Incorrect. networkd is tailored to specific purposes (largely containers) and not a general-purpose NetworkManager replacement, nor does it necessarily deprecate any ad-hoc network configuration scripts (which aren&#x27;t even intrinsically bad).<p>[1] <a href="http:&#x2F;&#x2F;blog.darknedgy.net&#x2F;technology&#x2F;2015&#x2F;09&#x2F;05&#x2F;0&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.darknedgy.net&#x2F;technology&#x2F;2015&#x2F;09&#x2F;05&#x2F;0&#x2F;</a>