I must be a new minority or something. At first I followed all of the arguments against SystemD, but just for shits and grins I tried Ubuntu Server 15.04 in its default configuration when I built three new network appliance VMs and...I actually like the result. I never did figure out how to get upstart to reliably make e.g. rtorrent restart when it crashes (and it crashes a lot) with upstart, whereas with systemd its crash recovery seems flawless, and it was easy to configure (you just need one line.) It was also very easy to tell it to wait until NFS was actually accessible before starting (upstart only gives you the ability to check that the NFS service is running, not that the NFS partitions actually mounted first.) With upstart I had to hack together a bash script that checked if NFS was mounted and then launch rtorrent as just a regular (non service) process.
Not only that but I was also impressed by how fast the reboots happened as I was setting up these VMs. Namely, I could open a new putty session to the server immediately after I issued the reboot command and closed the last one, whereas with upstart I would wait at least a minute or so. Now I no longer feel tempted to keep the vsphere client open just to watch its progress either.
Of course, I'm not a Linux guru as this server is mainly working as hobby tool and as a lab tool for running Cisco CSR1000v's for my CCIE training (though the server ONLY runs Linux, vSphere 6.0, and Cisco IOS, so I guess unlike most power users I have no dependence on Windows.) So having said that, I'll still defer to somebody who is a Linux guru for better judgement on systemd.