systemd isn't perfect, but it's definitely a net plus for me when compared with older init system. In case anyone's interested, this talk summarizes the key points pretty well: https://www.youtube.com/watch?v=o_AIw9bGogo
I am not interested in being preached at unless you have a workable alternative and a good reason why should I switch over.
I just use systemctl because I know how to use it and know all the ins and outs of any bullshit I might encounter. No way I'm switching. I like not being stumped on issues I can't fix for weeks.
As an OpenRC user, Systemd is fine. I prefer openRC but I have systemd on my server and all its LXC containers and I have had no issues with it.
Ok, but listen, though, systemd is the embodiment of evil...
If you think the init wars are stupid, take a look at the FSF people's (attempted) war against Libreboot and their absolute humiliation by the project leader..
I just use whatever that does the job. Sometimes I switch to systemd free distros just to know what it's like (currently checking out dinit version of Artix)
I think most of the discrimination arises from a way of thinking which puts minimalism, simplicity and speed as the first priority and starts a unhealthy obsession over it. Sometimes keeping things too minimal can require more work than doing the actual work. This can also be seen in people who rave about WMs vs DEs and Wayland vs X.
Oh and I use XFCE btw. I feel like that's the DE which gives me enough control over everything while not bombarding me with a truck ton of settings. I started using DEs again because I was spending all my time ricing away with window managers (and none of my rices were not even that good).
At the level I care about, which is "I want this daemon to start when I boot up the computer", systemd is much better. I can write a ~5 line unit file that will do exactly that, and I'll be done.
With init, I needed to copy-paste a 50-line shell script that I don't really understand except that a lot of it seemed to be concerned with pid files. Honestly, I fail to see how that's better...
Ubuntu btw
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.
"systemd is fine" yeah fuck you personally.
