It's odd that you included systemd in the list. It's something that a casual user isn't going to notice, but that has made life easier for system administrators and desktop tinkerers. With systemd, I can write a few lines of config to turn a simple Python script into a daemon with syslog integration, process monitoring, and resource limits. I understand the concerns about scope creep, but I'd take systemd any day over the maze of distro-specific shell scripts that was there before it.
Systemd definitely belongs in the list, even if some admins like it.
"Windowsification" is a admittedly vague concept, but tends to cover software that is gratuitously different, not a team player in the bazaar, prone to making land grabs through "embrace and extend", and reluctant to offer configuration options that conflict with its "opinionated" stances.
As an aside, I'm really sick of the systemd / "random pile of shell scripts" false dichotomy. It's trivial to turn a python script into a system service with runit, too. Simple, stable, and focused.
Systemd was widely adopted because it makes life easier for the distros. It is directly resulting from the increased popularity of Linux putting an increased demand on them.
