It's not switching RIGHT NOW either. As the mailing list post states "once the 'Missing systemd units' is over". This can still takes some months at worst. +Mike Herwig
Not really. I migrated 3 systems in one day. Only had problems with one, and those were solved in ~30 minutes with help of the Arch wiki.
And while I don't think systemd is perfect (lots of bloat… reduntant syslog implementation, e.g.; debugging is a bit more difficult than sysvinit, but it's manageable), the benefits are really, really aweseome. 2 seconds boot time (from bootloader to login screen) on a HDD, despite encryption? Yes please. Easy way to automount FUSE-bases network filesystems? Yes please.
The old sysvinit is really starting to show its age. The speed is abysmal, and you easily run into race conditions (unless everything is booted sequentially, which easily increases boot time by one magnitude).
Debian's attempts at implementing modern features (dependency-based boot, e.g.) in sysvinit just show how dead it is. Dep-based boot in Debian is even more cumbersome to configure than systemd and *never* properly worked for me. I still had 20+ seconds boot time and a weird, nontransparent command based configuration.
Additionally, classic rc.d initscripts tempt the programmer to move program logic into the init script. This makes debugging nigh impossible and really sucks if you have to port it to a different init system (Debian → Arch e.g.). Systemd's unit files are much cleaner.
The configuration is a bit less transparent than before, but as noted, even with sysvinit it never was "*everything* is configured over rc.conf". You had 15+ config files anyway. Now it's 20+, meh. Who cares. This is Arch. You set it up once and it works for the next 5 years.