What is starting processes isn't so much the issue. The issue is that systemd is demanding major changes of other software to work with it, and this is then making this software non-portable. e.g., Gnome 3.
People don't want to run Linux everywhere. Despite what some people think it is not always the best fit. There are other Unix platforms which fit better. Platforms that have had application compatibility with Linux up to this point. systemd has changed this. Changes to Gnome to work with systemd for example have made it non-portable to other platforms.
This is a problem for anyone who wants to say, develop a cross platform gnome3 application.
That, and there are the corruptable binary logs, the solution to which in the bug report is to "just delete them" and the bug has been closed as won't fix. Sorry, but if this is the resposne to journal corruption rather than finding out WHY the journals get corrupted and fixing the fuckign problem, then i do not want that in control of my logfiles.
Also, the massive violation of the KISS principle that has been a core guiding principle of Unix design since the start.
Systemd is a poor solution to a non-problem. There are plenty of other problems to tackle first, before trashing and re-writing working, well debugged code and breaking cross platform compatibility for no good reason.