this post was submitted on 14 Sep 2024
1400 points (96.8% liked)
linuxmemes
24686 readers
1367 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think it is breaking the Unix philosophy, it is an enormous piece of code that does so many different things. My ideal is smaller components with smaller dependencies. When distros or software becomes inextricably dependent on systemd they are then beholden to whichever direction the maintainers take it.
My take on it is somewhat based on "what if." Other people have some pragmatic discussions on security aspects if you search around.
I'm not a systemd guru, but I do find it relatively easy to work with.
I've noticed that a lot of it is actually made up of separate binaries and daemons. Is it wrong or misleading to think of systemd as a collection of utilities that share a common DSL as opposed to a strict monolith?