I never liked it or its cumbersome cryptic companion, journald.
My biggest issue with systemd is the fact that it relies so heavily on binary logs and crap like that, which completely breaks the Unix paradigm. Log and configuration files should be human readable. If you want Formatted data that is easily parsed problematically, that is fine, but logs MUST be easily read and understood by human beings. You should be able to use all the standard text processing tools like grep,sed, and awk against them. If you can't grep for a regex, your logging is absolutely broken.
Similarly, you should be able to walk through your init and determine exactly the order everything should start in. I generally find systemd to be opaque and generally a mess to walk through.
Indeed. I put this in as a weekly crontab. You'd be amazed at how much space you recover, especially the first time you run it.
#!/usr/bin/bash journalctl --disk-usage journalctl --rotate journalctl --vacuum-time=7d