Systemd, ten years later: a historical and technical retrospective
My beef with systemd is not its reinventing things. That part may actually be good.<p>One problem is that a number of reinventions were poorly made.<p>E.g. the log format. Yes, unstructured logs have a ton of drawbacks. Can we take some ridiculously well-tested, reliable embedded database or serialization format (like sqlite) and use it as log storage? Alas.<p>Another problem is the &quot;I know better&quot; attitude.<p>Are user processes allowed to run after logout? Which DNS to use during startup? What logging in should look like? In each such case, existing behavior which was <i>widely considered as not broken</i> was replaced by a different behavior, often even without an escape hatch.  The new behavior(s) in such cases should be made possible, but the default should be the old behavior.<p>No wonder I don&#x27;t run systemd on my desktops &#x2F; laptops.