this post was submitted on 19 Apr 2024
885 points (98.7% liked)
linuxmemes
19748 readers
2045 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's also "infectious" software. The way systemd positions itself on the system, it can make it more difficult for software to be written in an agnostic way. This isn't all software, and is often more of a complaint by lower level software, like desktop environments.
https://catfox.life/2024/01/05/systemd-through-the-eyes-of-a-musl-distribution-maintainer/ This isn't a terrible summary of some of the aspects of it.
Another aspect is that when it was first developed, the lead on the project was exceptionally hostile to anyone who didn't immediately agree that systemd definitely should take over most of the system, often criticizing people who pointed out bugs or questionable design decisions as being afraid of change or relics of the past.
It's more of a social reason, but if people feel like the developer of a tool they're forced to use doesn't even respect their concerns, they're going to start rejecting the tool.
What do you expect from an init system? It's like saying my cpu is infectious because my computer depends on it
I think the init system is the best part of systemd. It is sooo easy to use. You don't have to write the same complicated shell script for your software like everyone else. You just give systemd the path to your executable and that's basically it. It does the rest and you don't have to worry about PID files or forking the actual software. Systemd basically runs it like you did while developing it.
I think what people don't like are all the other parts of systemd that seem to be tightly coupled. I don't know if it is even possible to run just the systemd init without any other systemd package.
The last time I got angry at systemd was when resolvd did some DNS shit I did not approve of.
I may be wrong but I believe that all of the systemd programs are decoupled. You can run the systemd init system without any resolved or networkd. They just happen to be used by default on a lot of distros.