For a desktop it's suitable for 99% of what you'd want to do. Might not be the best tool for large servers or something (I really don't know) but I'm sure all that depends on use case.

I don't have anything against systemd that is until I tried void linux for the first time. The working of runit seemed very simple and efficient compared to the complexity of systemd.

I still don't hate systemd, but I just wish it was simpler.

The arguments against systemd come from the same people that love IRC, mailinglists, tiling window managers, split keyboards, don't have a mouse, debug with printf, main arch or gentoo, unironically write RTFM|LMGTFY, call users "lusers", play DnD, think Startrek and/or Star Wars cannot be topped, identify with the portrayed super hackers in media, and are proud of doing things the hard way just to feel some kind of superiority in their life.

Edit: for those who don't get it, I'm obviously not being serious. If you fit this mythical, stereotypical person... uh... good job?

I feel like, at this point, it has more than proved itself as a general purpose desktop scheduler. But there are situations where you would want something different but a lot of software depends on it anyway.

I also kinda don't understand the hate toward the project itself, other than hearing some of the technical guidance on it has been a bit arrogant in the past or something. Sounds like sily open source drama to me honestly.

I only hate it because I can't figure out how to run a blocking script before everything else when a suspend is initiated.

Linux power-users hate it when a tool tries to become a platform.

It breaks the principle of single responsibility and becomes a threat to the evolution of alternatives.

It's pros and cons. Having a platform is better because everyone works together on a single effort. But it also becomes a risk because now everyone depends on a single thing that does too much.

You're 10 years too late. We're all on the systemd bandwagon today.

What else are you going to do? runnit? 😭

It's a pretty bridge, they'd say, but be careful you don't look at the supports. It was built using bad techniques, bad procedures, no coordination and no inspection.

Just cross your fingers as you drive over and hope it doesn't blow up because of its flawed construction.

I find it's a great way to cross the river, today.

Every new tools (especially those being pushed by big corporations) meets resistance and suspicion. It's a new thing to learn instead of something proven to work, usually more resource-hungry...

I find everything so complicated with systemd.

SysV was just intuitive for me and my knowledge. There was just one directory with all the startup scripts in it. And they were run in their alphanumerical ordner. Just that simple. If I wanted to change the order in which the scripts started, I just had to rename the file. You don't want a script to run at all? Just remove it.

I assume, systemd has many advantages for a knowledged user. But for me, it still is just a hassle.

What's up with the username?