And welcome to the appeal to emotion fanboy rant, thx for proving my point. BTW noticed how you completely avoided what Lennart wrote on his blog, lets see what this "simple replacement for init" is morphing into, shall we? Lennart's own words...
"The tasks mentioned that systemd already covers include, "init system, journal logging, login management, device management, temporary and volatile file management, binary format registration, backlight save/restore, rfkill save/restore, bootchart, readahead, encrypted storage setup, EFI/GPT partition discovery, virtual machine/container registration, minimal container management, hostname management, locale management, time management, random seed management, sysctl variable management, and console managment."
"Tasks being worked on are support for a local DNS cache, mDNS responder, LLMNR responder, DNSSEC verification, IPC support in the kernel (KDBUS), time synchronization with NTP, better integration with containers, and many other services. "
Think he can shoehorn anything else in there? And FYI every other replacement for init that was credible is dead or dying, the devs are running like squeeing fangirls to systemd...which is why every large Linux server admin I've talked to is already talking exit strategies and trying various *BSDs looking for the one to replace their current setup.
Oh and you just gotta love that the Phoronix article I got his quote from felt the need to bring up as I did the comment fixing and even some of the kernel devs are getting fucking sick of showstoppers in systemd....yet its still getting rammed through....huh. Has the check cleared from RH and the NSA or is this just a freebie?