Oh this makes me really happy. I don't know how others experience has been systemd, but in my experience, and as a daily user of it, I get more and more frustrated with it.

I'll preface this with saying, I do fundamentally understand the need for a new init. There is no question that SysV has run it's course, and we could use some refreshing in that area.

My problems aren't even with using systemd as an init system, for example, I have no problem with Unit files, or the like. What I have a real problem with is the way it tries to octopus into the system. I don't want binary logs, I don't want my init system logging at all! I don't want udev in my kernel, that to me is clearly a user space IPC, there is no benefit that I can see moving it to the kernel!

My biggest problem just stems from moving from the idea of "Do one thing and do it well" to the idea of "This software will do everything for you!"

I don't want my software to do everything for me. I want to know that if something breaks, I can determine it's part of x, y, or z.

Even as I was writing this I had a problem where my wireless dropped. Why? I don't know, I checked journalctl, nothing there, dhcpcd didn't show any errors, should I assume it was systemd reconfiguring some utility?

I want systemd the init system, not systemd the computer mom. I don't need a computer mom. My mom never liked computers.