There are CONSTANT statements that if you do not use systemd you will not be able to use primary Linux distros in the future, because all software will supposedly be gobbled up by it as a dependency... To try and now make out like those dont exist is pretty silly.
not "supposedly" - *really*. if you run apt-rdepends -r libsystemd0 | a bit of awk | sort | uniq there are four *THOUSAND* five hundred packages that, if you were ever to do "apt-get --purge remove libsystemd0" you would NEVER be able to install. that's a whopping FIFTEEN PERCENT of the entire debian package repository that you are prevented and prohibited from installing, should you ever make the decision that you wish to keep libsystemd0 off of machines that you manage!
the reason for this insane level of *hard* dependency is because lennart pottering is both the developer of libsystemd0 *and* many other packages such as pulseaudio... so of *course* he decided that pulseaudio had to include - as a hard dependency - one of his projects, libsystemd0. libsdl likewise also uses it as a hard compile-time dependency, along with about 100 other applications and libraries.
those applications and libraries then quickly spread as further hard dependencies to include the gimp, apache2-dev, php5 (??!), erlang, libreoffice, cups, bluez/bluetooth (because of the links to pulseaudio), *all* the games that use libsdl (i.e. pretty much all of them), *all* the music software available for GNU/Linux (because of the link to pulseaudio), openjdk7, the eclipse IDE, apache tomcat, the android SDK, i mean.... the list is a _real_ eye-opener. you can review it here for yourself:
so yeah, not even _close_ to "supposedly", mate!