I also want to use my computer and not think about init systems. That's a large part of the reason why I don't like systemd.

I use Gnome.

i use swayfx and runit

i don't like systemd because it has a lot of stuff that i don't think should be built-in, for example, why have systemd timer when cron already exists?

runit is nice for me because it's simple and i like activating services by just soft-linking files to /var/service instead of using some fancy tool

I've got no clue what systemd is lmao

I see way more posts that are pro-systemd than anti these days, so I think you might be tilting at windmills a bit.

I would love to think about systemd less, but I've worked with it professionally since a year or so before Debian switched while I was an intern working in embedded. I got to see the flame wars and shaped my opinion of systemd by wrestling with its growing pains. Writing your own service files and working with DBus was ass back then, and while it has gotten better, my patience with it has diminished. In the end the frustration was enough that after I ditched windows, systemd was the next to go.

That would be the end of it, but other programs keep growing annoying systemd dependencies or their projects get swallowed up by the systemd ecosystem entirely. I was so excited at the start to work with the parallel execution and dependency management, but the number of times systemd broke something, swallowed up the output, and then corrupted its own journal and lost the logs really turned me against it.