A more accurate description would be "Systemd is a set of building blocks that you can use to make Linux more like Windows".
A more accurate description would be "Systemd is a set of building blocks that you can use to make Linux more like Windows".
As far as I can tell the only "windows-y" thing is binary logs and even then you got all the tools to get a plaintext stream to process. Corruption of the logs can be a problem but it's nothing compared to...dunno, I assume people are drawing parallels to that and Windows' binary Registry, but then again I don't think I have had a Registry-related failure in decades. Besides, if anything, dconf is much more Windows than anything systemd could do, but I don't see anywhere as much vitriol for it.
I'm thoroughly confused about this small war with systemd. I missed all the early drama so I barely know what it's about, but in practice systemd has never failed me.
What I want is a solid system that does what it's supposed to -- start stuff -- in a maximally boring fashion.
While I prefer Linux in general, Windows does have some good ideas in some places, and I don't see any issue with using them.
systemd was in fact heavily inspired by MacOS's launchd. At worst, it can be said that complex boot managers will begin to converge on a design that actually works ~ MacOS did, Windows did, and now Linux has with systemd. The three have plenty of differences, though systemd is still closer to launchd than not.
And in actuality, it's very tweakable. Did you notice that the source code is open, for a start...?