Hm? What's wrong with systemd? I don't remember it ever getting in the way or doing stuff that required a week of googling to fix and the fix getting undone with the next update.
For desktop workloads systemd tends not to be so bad. For server workloads it's a huge pain in the hindparts. If a daemon listens on a given port, systemd will itself listen on that port, and then forward everything that comes in to the daemon. If the daemon crashes for any reason, systemd will continue listening on that port. So if, for instance, you're trying to diagnose a crash and are using a different command line than the default command line that systemd uses to start the daemon, you can't just open up a terminal, type the alternate command line, and have everything work: you have to specify a different port, or systemd will eat all inbound traffic for that daemon.
Then there's systemd's habit of, under certain circumstances, eating full CPU on one core. I've never had an issue with it on my main desktop, but it was the final straw that led me to rip systemd out and replace it with sysvinit on a Raspberry Pi GPS timeserver that I was setting up.
I never got why, around the time I was getting involved with Linux, everybody was hating on Pulse Audio. I'd never had any problems with it, and still haven't. Now that I've been burned by systemd a couple times, I understand: Lennart Poettering writes crap software and won't listen to criticism.