I dont see an issue with systemd,
the issue isnt with systemd per se, the issue is systemd becoming a dependency of things that should not require it. for example, since systemd decided to eat udev, that means that every package that used udev now needs systemd. if you use any of the major desktops, it is a requirement. one the upside, it's fuelling the development of other desktops environments.
... let people who do not want systemd simply configure their system either so that systemd will start regular sys v init or bsd type scripts, or let them change /bin/init to point to the alternatifve init system of their choice.
there is a problem with that, it means systemd is running. there is an additional opposition to systemd itself, the most universally relevant reason being that systemd has a HUGE attack surface. the other reasons all feed into this one issue, it's a blaring and blindingly bright security issue.
btw, if you are GNOME2/MATE holdout trying to escape systemd like me, consider using LxQt. it's still a work in progress but it's usable as an everyday desktop environment.
LxQt repo (works with debian jessie):
deb http//ppa.launchpad.net/lubuntu-dev/lubuntu-daily/ubuntu/ utopic main