• PieMePlenty@lemmy.world
    link
    fedilink
    arrow-up
    15
    ·
    9 hours ago

    The thing about CLI is that everything is hidden by default. You come to the application with your own mindset and a goal in mind and you figure out how make it do what you want.
    When there’s a GUI, you often see everything that’s possible from the start and so the application dictates how you use it.

    Though, you can do either with CLI and GUI as well. That’s the sweet spot I think is the best. I love it when a CLI app guides the user through a process and gives options. And a good GUI should disable OK buttons and show validation errors if not everything is entered correctly.

    In a perfect world, every app has a CLI mode, interactive and non interactive and a GUI mode with full validation and responsive UI changes. But realistically, good UX is what we need, either GUI or CLI.

    • Someonelol@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 hours ago

      Also CLI interfaces are a lot like having to know a language with the right keywords and vocabulary. Sometimes the manual doesn’t always list out all the commands so it takes some trial and error to figure out. You can easily change something you didn’t want to as you do.

    • MrScottyTay@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 hours ago

      This is one of the reasons why I can’t migrate from visual studio to VS code for work. Everything is hidden beyond the weird palette search bar thingy. Just give me drop down menus and toolbars please. I’m stuck of having to remember shortcuts for things I don’t do often enough to warrant it taking space up in my very limited pool of memory