On the desktop where you need to deal with WLAN interfaces going up and down, maybe a monstrosity like systemd has its place, but even there my opinion is systemd just isn't worth fragmenting and polarizing the whole Unix ecosystem with systemd's total lack of mental discipline and attitude of wrapping each and everything under the sun including binary logging, mandatory systemd-only APIs for loggin in, cron replacement, etc.

On the server-side where Linux has its mainstay, using systemd is even more pointless IMHO since services and network interfaces don't come and go. Loosing portability for saving a couple lines of shell code for starting/stopping services is IMHO a trade-off that just doesn't make sense from an engineering PoV. All the more so since systemd doesn't shield you from the intricacies of dealing with demon programs; if something is going south on your server, have fun with systemd binary logs to analyze what has happened.

Now RedHat (who are shouldering a large part of Linux development anyway) sure aren't stupid; therefore I have to conclude that they're playing the Embrace, Extend, Extinguish game here to subvert Linux into SystemD-OS.

Devuan has become a very important key project to prevent that from happening to the Debian code base. Btw congrats to the Devuan project! I wasn't quite sure they'd be able to deliver a couple years ago when they started; now I think Devuan (along with Gentoo, Slackware, Alpine) is going to save Linux' ass as a "real" F/OSS community effort going forward, no less. My hope is Arch Linux with its great community and documentation gets a systemd-less fork as well.