Okay, but why go about it that way? That can't be the only way of making a viable alternative to sudo. Why does everything need to be part of one project? If you want to reuse code why not spin it out into a library so each component can be installed with just the libraries it needs and not the depending on the whole gigantic thing? KDE works that way. It's obviously possible for some things, at least.

One of my favorite things about Linux is simply fiddling around and finding the things I like and don't and just using the ones I do. I can't do that effectively with systemd though. Sure, it's theoretically modular, and there are even a couple parts left that can work independently, but mostly it's just one big block of half an operating system that all gets lumped together into one gigantic mess, and I can't effectively just use the bits I like. It's kind of all or nothing, and then maybe being allowed to double up on some of the things I'd like to use an alternative to... for now. It just kinda sucks the joy out of using my computer, but trying to avoid it completely is a massive pain in the butt.

There's no big dramatic thing wrong with systemd. Using systemd and being happy with it is a good thing. I do not object to the existence of systemd. Systemd is fine. It just makes me like Linux less is all. I am enjoying my time with my computer less than I used to, and the universal dominance of systemd is probably the biggest reason for that.