Part of the reason for a command line is being able to reproduce commands exactly. Going back through the command history is an important part of that.
For a while I was using a VPN where the connections we all via command line. I loved it, because once you type it, it’s just up up up to find that location again and swap around.
Now I have to use the mouse and click like a damn fool!
In my first professional programming job writing custom software for clients in 1995, one of our standard sales pitches to clients was the idea that a GUI-based application would do away with the need for command prompts. This was always met with applause and great rejoicing. It’s kind of remarkable that command prompts are still going strong thirty years later. I’m sure nobody would appreciate having this phenomenon compared to the Amish so I won’t do it. But I think it’s pretty cool that the Amish are still around doing their thing.
A GUI makes sense if you want things to be approachable. A CLI makes sense, if you want things to be well customizable.
E.g. compare LaTeX script with setting formatting in an office program. Yes i see directly how the formatting is. And if a good Formatting standard is set, it can be used quite well nowadays. But if just want to put one Paragraph differently in order to fit a picture or table or something then things quickly get messy.
I thought command line users like typing things. I avoid typing where possible, and dont use the command line on Linux.
Part of the reason for a command line is being able to reproduce commands exactly. Going back through the command history is an important part of that.
For a while I was using a VPN where the connections we all via command line. I loved it, because once you type it, it’s just up up up to find that location again and swap around.
Now I have to use the mouse and click like a damn fool!
I work as a software developer. My team mate once said he was a “mouse and click kinda guy” when asked why he didn’t use the terminal for git.
Ugh, I bet he never pressed CTRL + C or P in his life.
In my first professional programming job writing custom software for clients in 1995, one of our standard sales pitches to clients was the idea that a GUI-based application would do away with the need for command prompts. This was always met with applause and great rejoicing. It’s kind of remarkable that command prompts are still going strong thirty years later. I’m sure nobody would appreciate having this phenomenon compared to the Amish so I won’t do it. But I think it’s pretty cool that the Amish are still around doing their thing.
A GUI makes sense if you want things to be approachable. A CLI makes sense, if you want things to be well customizable.
E.g. compare LaTeX script with setting formatting in an office program. Yes i see directly how the formatting is. And if a good Formatting standard is set, it can be used quite well nowadays. But if just want to put one Paragraph differently in order to fit a picture or table or something then things quickly get messy.
GUI is great, unless you want to automate something… Then you either want a CLI or API
Nah, companies found solution to that long ago.
…
…HOW’S IT GOING JOHNY, GOT THAT LIST PARSED YET?
People do not just point and nod. Using words and not just guestures makes life easier in many, but not all situations.