The Debian technical committee vote concludes

> And above all, would I really gain anything practically useful by doing this?
Well, you'd get the journal, which IMO works much better than classic plain text log files.
Check this out: http://0pointer.de/blog/projects/journalctl.html
I also love the way it's configured. For example, packagekitd used to hog my CPU and IO bandwidth at the most inappropriate times. So I dumped the following lines into /etc/systemd/system/packagekit.service.d/bla.conf:

[Service]
CPUSchedulingPolicy=idle
IOSchedulingClass=idle

Voila, problem solved.And even if a package upgrade modifies the configuration file (/usr/lib/systemd/system/packagekit.service), it won't affect my changes at all. This is only possible because systemd's configuration files are entirely declarative and don't contain any executable code. systemd-delta can show you how the configuration in /etc affects the default configuration shipped in /usr/lib/systemd. For the above example, it prints the line
[EXTENDED] /usr/lib/systemd/system/packagekit.service → /etc/systemd/system/packagekit.service.d/bla.conf

My personal experience is that pretty much regardless of what you want to do, systemd usually offers a much cleaner, terser, more comprehensive and easier solution than what you have to do with sysvinit.