• endless_nameless@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    1 day ago

    It’s pretty easy to explain why people prefer CLI over GUI programs. You have to learn a new interface for every single GUI program, whereas you learn one interface for every CLI program.

    • Natanox@discuss.tchncs.deOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      22 hours ago

      That’s just wrong, the correct commands are always different. E.g. for journalctl to keep following the newest entries you need -f, while in dmesg you need -w for the very same feature. That’s not any more “the same” than it is the “same” to move your mouse around a differently organized GUI.

      Writing in the CLI is comparable with moving the mouse, and remembering the appropriate commands of the specific tool comparable to know where to click on. However a proper GUI is immediately visible to be interacted with (and not abstract like most CLI arguments) and will convey function through form, while the function in the CLI is hidden behind help texts and man pages.

      I do like working with the CLI a lot, but what you said was simply wrong.

    • silt_haddock@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 day ago

      CLI requires remembering commands though, or developing patience with your up arrow key.

      And if you want help, is it “/h” or “/?” or “-h” or “—help” or “—h” or just “help”

      I can’t remember that I need to pee, let alone what commands do what, save for my up arrow.

      Don’t get me wrong, I’m in the terminal constantly, but I’ll pick a GUI over CLI every time if it’s an option.