Re: *I* propose ...
... doesn't need to take over logging, cron, device management, DNS, hostname provision, network management, interprocess communications, home directory management, ntp, container management, and everything else ...
Like I have said before:
Systemd is a virus, a cancer or whatever you want to call it. It is noxious stuff.
It works just like the registry does in MS operating systems.
It's a developer sanctioned virus running inside the OS, constantly changing and going deeper and deeper into the host with every iteration and as a result, progressively putting an end to the possibility of knowing/controlling what is going on inside your box as it becomes more and more obscure.
Systemd is nothing but a putsch to eventually generate and then force a convergence of Windows with or into Linux, which is obviously not good for Linux and if unchecked, will be Linux's undoing.
There's nothing new going on here: it's nothing but the well known MSBrace at work.
Now go and tell me that Microsoft has absolutely nothing to do with how systemd is crawling inside/infecting the Linux ecosystem.
This started over 25 years ago and was finally put out into the light thanks to the infamous 1998 internal MS report.
Like if the browser wars were not enough to catch it.
It is in many ways understandable that the problem at hand is still absolutely transparent for the every day home user who only wants to browse, chat, send web mail, watch porn or play games.
By the time it is evident to them it will be far too late to do much about it.
But anyone else ie: involved with their PCs/servers/etc. installations and with a modicum of experience with their hardware who at this stage does not understand what has been/is going on has their brain-box either buried in the sand or up their ass.