Sure. Systemd was brought in around a decade ago on many of the large Linux distributions to replace sysvinit which had been the dominant init system since...maybe ever? Definitely the late 90's anyway. It was a mess of tangled shell scripts on most of these systems, so it's not totally shocking that they made the shift, despite the fact that systemd is in many ways not in line with the Unix philosophy of "do one thing, and do it well."
The issue is that we started seeing software packages start building out as a dependency, as if Linux meant systemd was a given. Except it doesn't, and hopefully never will. Gentoo uses OpenRC, Slackware uses BSD style rc scripts with sysvinit, Void uses runit with some support for alternatives. To name a few of the larger systems (all of which I'd argue are a heck of a lot more pleasant than the Debian and Redhat based world).
I'm particularly salty today because I have been diving into FIPS and Reticulum and it turns out that while FIPS will fun on ANYTHING from openWRT to windows to OS X to even Android, it's got systemd as a dependency for desktop Linux.
The idea that any of this software should be tied intricately to the init system is wild. Modularity is a tradition going back to the 70's in the Unix tradition, and systemd is a slap in the face.
