• jj4211@lemmy.world
    link
    fedilink
    arrow-up
    4
    arrow-down
    3
    ·
    4 days ago

    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
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      4 days ago

      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
        link
        fedilink
        arrow-up
        2
        ·
        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.