this post was submitted on 12 Nov 2024
122 points (83.9% liked)
Linuxsucks
209 readers
50 users here now
Rules:
- FOSS advocates and Linux evangelists aren't welcome. -We ask that you block us.
- Moderation is heavy handed. Try to stay on topic.
- No Complaining Mute the sub if users, content, or rules bother you
founded 2 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
People bitch about systemd? Don't pretty much all the major distros use it?
People bitch about it because of it's wide usage in a system. But distros like systems because it has a wide usage within a system.
Yes, most of them do, and that is why I complain about it. I want to have the choice. I don't mind if other people use systemd; I just don't want it forced one me.
Gentoo, Arch, and their derivatives still exist. How important is a legacy init system to you?
FYI: Arch uses systemd.
I don't mind systemd so I haven't tried to rip it out, but I can't imagine trying to replace it with a legacy init system is going to be smooth sailing.
Probably true, but Arch being what it is, there's still the option to install sysvinit or whatever. The question remains - how important is NOT using systemd to the admin in question?
Yes, and that's the FUNNY part about it! Lennart went against the UNIX philosophy and is hated for it, but so did Linus Torvalds with the monolithic kernel, and Richard Stallman with Emacs.
The "do one thing and do it well" mantra is such bullshit. You can slice up the things stuff does differently however best suits your argument. Oh,
wc? I don't use it because it violates the unix philosophy. It can count words and lines. That's two things.And systemd don't violate it, systemd is the name of the project with a bunch of binary inside each onde doing their job, it's like complaining that Mesa don't follow Unix philosophy just because it has multiple drives inside the project
The Unix philosophy never made sense.
All parts of a program should do one thing well and communicate with other modules over a simple, common interface.
But software that offers all the features a user will need under a big umbrella with unified UI and UX is much better than "this program uses different syntax because it came from Unix and not GNU"
Yes and no.
A consistent UX is definitely a major bonus, but not if it comes at the cost of oversimplification. If the program gives me an experience gift-wrapped and with a nice little bow on top, but only gives me that kids' gloves experience, it becomes a much worse experience when you need to do anything outside the happy path.
Imagine trying to script
gitworkflows without access to any of the plumbing commands likerev-parse,rev-list, and format strings. You would have to parse the output ofgit logandgit show, hoping that they don't introduce a new change to the output—a much worse experience.Fun fact: you basically described dbus.
And one day you'll learn that 'popular' isn't often 'good'. I think we called it a Lithium Lick when Apple did it.