• squiblet
    link
    fedilink
    29 months ago

    “Guessing commands” isn’t the way to go about it. Read the man pages. Read the help for commands. Read a tutorial or some examples.

    • @[email protected]
      link
      fedilink
      English
      109 months ago

      That’s exactly my point. You can’t explore a CLI. You need to rely on external resource to first learn how to use it. That’s just not something you can ask of people who want to use computers as tools. When’s the last time you read your car manual?

      • squiblet
        link
        fedilink
        29 months ago

        Info pages, help and manuals are built into the system and commands. You don’t have to leave the shell to read anything. I’ve also explored it just by pressing a letter or two and then autocomplete. But you realize that average people need help to figure out a GUI too, right?

        A car manual is more comparable to learning how to drive in the first place. And yes, sometimes I’ve consulted the manual to figure out what lights mean or how controls work.

      • Semi-Hemi-Demigod
        link
        fedilink
        09 months ago

        Sure you can explore a CLI. It’s not unlike playing Zork. You can try something, read the response, and try something else. That’s how I learned the CLI outside of specific command attributes

    • @[email protected]
      link
      fedilink
      59 months ago

      that’s just extra friction, with UIs you can explore and figure out at a glance roughly what a button will do

      • squiblet
        link
        fedilink
        1
        edit-2
        9 months ago

        It’s possible to do amazing things with a CLI in seconds that would be minutes of clicking with a GUI - that’s why they still exist. And sure, it’s tuned towards people who would be “how about I write a Python program to handle this”.