And don't forget to mention that systemd still does not work properly. I haven't had a single systemd-based system that would not show non-deterministic behavior.
I started on Arch where it lead to a system that could not boot sometimes and was impossible to shut down (ACPI broken, even with the 5sec power-switch trick, it just rebooted! I don't even know how the hell this was possible... the system was like possessed! the only way to power off was the switch on the ATX power supply during reboot).
The other Arch system could not mount NFS shares at boot. Race condition with network interface initialisation. Googled up some really exotic fstab flags, but systemd-based boot ignored them completely. ACPI was also broken, of course and there have been some other problems with services not starting properly.
Now on Debian (in Virtualbox), I have the problem that every 4th or 5th boot slim is starting but I cannot type anything. It looks like the keyboard is not initialized and slim is already started. At least ACPI works, so I can send Virtualbox Hotkey+H to make it shut down cleanly.