this post was submitted on 12 Nov 2024
121 points (84.2% liked)

Linuxsucks

188 readers
76 users here now

Rules:

  1. FOSS advocates and Linux evangelists aren't welcome. -We ask that you block us.
  2. Moderation is heavy handed. Try to stay on topic.
  3. No Complaining Mute the sub if users, content, or rules bother you

founded 1 month ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 2 weeks ago (1 children)

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"

[–] [email protected] 4 points 2 weeks ago

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 git workflows without access to any of the plumbing commands like rev-parse, rev-list, and format strings. You would have to parse the output of git log and git show, hoping that they don't introduce a new change to the output—a much worse experience.

All parts of a program should do one thing well and communicate with other modules over a simple, common interface.

Fun fact: you basically described dbus.