this post was submitted on 19 Apr 2024
888 points (98.9% liked)

linuxmemes

20880 readers
6 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
888
systemdeez nuts (sh.itjust.works)
submitted 7 months ago by [email protected] to c/[email protected]
206 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 60 points 7 months ago (1 children)

My understanding is that some people are die hards to the software philosophy of "do one thing really well". systemd at the very least does many different things. These people would prefer to chain a bunch of smaller programs together to replicate the same functionality of systemd since every program in the chain fits the philosophy of "does one thing really well".

[–] [email protected] 47 points 7 months ago (3 children)

For me it’s 3 things

  • Do one thing and do it well
  • Everything is a file in Linux
  • human readable logs

Systemd breaks all three of though by being monolithic and binary. It actually makes you have to jump through more hoops to do things in certain cases. I understand it’s a mindset shift but it really starts making it feel more like Windows with how it works and the registry and event log.

[–] [email protected] 13 points 7 months ago

I don't see how systemd has anything like the Windows registry. At least its journals are leagues ahead of Windows event logs, I hate those things and the awful viewer they have.

[–] [email protected] 4 points 7 months ago

like Windows

systemd-bsod is incoming

[–] [email protected] 3 points 7 months ago

You forgot: use as many dependencies as you need. For example, my init system does not use xz-utils.