this post was submitted on 27 Mar 2025
999 points (90.7% liked)

linuxmemes

24192 readers
1871 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe 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.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    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
    [–] ftbd@feddit.org 29 points 5 days ago (2 children)

    There are definitely people who think it is reasonable to memorize button locations and 10 levels of menus in GUI programs but would rather go into cardiac arrest than use something like program --option input-file output-file.

    [–] endeavor@sopuli.xyz 20 points 5 days ago* (last edited 5 days ago) (3 children)

    thing with gui is you don't need to memorize button locations and menus. If you do it's poor layout. Good gui lets you find things you didn't know you were looking for intuitively, without external resources or manual. CLI requires you to know what exactly you are doing and is impossible to use without external resources. Nothing against terminal but unless you know what you are doing and every command required to complete that action, it's ass. If gui was so bad and cli was so good, guis would not be used by anyone.

    I mean you dont go around copy pasting device ids and running commands for 20 minutes to connect your device through terminal when it is done with 2 clicks in the gui even by someone who has never used a pc before.

    [–] jj4211@lemmy.world 2 points 5 days ago (1 children)

    While you don't need to memorize button locations and menus, the frustration is that it takes longer, and memorizing those details slightly mitigates. It's torture helping someone do something while they hunt for the UI element they need to get to the next level of hierarchy. They will do it, in time, but it just feels like an eternity.

    The main issue in GUI versus CLI is that GUI narrows the available options at a time. This is great, for special purpose usage. But if you have complex stuff to do, a CLI can provide more instant access to a huge chunk of capabilities, and provide a framework for connecting capabilities together as well as a starting point for making repeatable content, or for communicating in a forum how to fix something. Just run command "X" instead of a series of screenshots navigating to the bowels of a GUI to do some obscure thing.

    Of course UI people have generally recognized the power and usefulness of text based input to drive actions and any vaguely powerful GUI has to have some "CLI-ness" to it.

    [–] endeavor@sopuli.xyz 3 points 5 days ago (1 children)

    Sure terminal can be better in a few cases but the fact you are typing this from a guy browser on a gui os speaks for itself.

    [–] jj4211@lemmy.world 3 points 4 days ago

    Of course my terminals outnumber my browser tabs by about 3:1 right now. Commenting on an internet site needs neither scale nor complexity and a WebUI is fine for that.

    [–] jerkface@lemmy.ca 1 points 5 days ago

    The alternative to memorization is the analog to "hunt and peck typing" where you just search the whole fucking screen/program.

    [–] the_crotch@sh.itjust.works 8 points 5 days ago (1 children)

    As far as I'm concerned "windows key, start typing the name of the application" or "CMD+space, start typing the name of the application" is the right way to handle GUI. Apple nailed it with Spotlight and it's vastly improved Windows and a variety of Linux DE's

    [–] 0x0@infosec.pub 3 points 5 days ago (2 children)

    Uh.. Do you think spotlight was first doing search by typing from a hotkey..?

    What you're describing are basic menus and icon search. I honestly don't get what you're getting at with this at all, maybe I'm just dumb.

    [–] jj4211@lemmy.world 5 points 5 days ago

    I suppose the point is that the way people interact with GUIs actually resembles how they interact with CLIs. They type from memory instead of hunting through a nested hierarchy to get where they were going. There was a time when Desktop UIs considered text input to be almost a sin against ease of use, an overcorrection for trying to be "better" than CLI. So you were made to try to remember which category was deignated to hold an application that you were looking for, or else click through a search dialog that only found filenames, and did so slowly.

    Now a lot of GUIs incorporate more textual considerations. The 'enter text to launch' is one example, and a lot of advanced applications now have a "What do you want to do?" text prompt. The only UI for LLMs is CLI, really. One difference is GUI text entry tends to be a bit "fuzzier" compared to a traditional CLI interface which is pretty specific and unforgiving.

    [–] the_crotch@sh.itjust.works 3 points 5 days ago

    It wasn't the first, no. But it was the first that was commonplace and implemented well enough that others almost immediately adopted it.

    It's the same as the iPad. Tablets existed before the ipad. Nobody bought them until apple created a market for them. It's their biggest strength as a company.