←back to thread

In the Beginning Was the Command Line (1999)

(web.stanford.edu)
412 points conanxin | 1 comments | 27 Jul 24 06:25 UTC | HN request time: 0.208s | source
Show context
ndsipa_pomu ◴[27 Jul 24 12:50 UTC] No.41086243[source]▶
One major advantage of the CLI is that instructions/fixes etc are very concise and can be easily communicated. If someone has a Linux system that needs a known fix, then it's trivial to send someone the commands to copy/paste into a terminal. However, if there's a known fix for a graphical program, then it suddenly becomes much harder to communicate - do you go for a textual instruction (e.g. click on the hamburger menu, then choose "preferences"...), or a series of screenshots along with some text?
replies(6): >>41086944 #>>41088283 #>>41088290 #>>41088405 #>>41089211 #>>41095482 #
gregw2 ◴[27 Jul 24 18:04 UTC] No.41088283[source]▶
Agreed. Poor scripting/replay inherently limits the GUI.

That said, the best late 90s expression of the core advantage of the GUI over the TUI/CLI is that it demands less of the user:

"recognize and click" vs

"remember and type"

That seems very fundamental to me.

I have not seen as succinct expression of tradeoffs for V(oice)UI or L(LM)UIs

replies(2): >>41088389 #>>41091586 #
1. dsubburam ◴[27 Jul 24 18:25 UTC] No.41088389[source]▶
How about the new kid on the block here, the chat interface? Neither "recognize and click" nor "remember and type", esp. if done over voice.

Maybe the chat interface does away with the first half of the GUI/CLI schemes, skipping over learning the affordance part of the interface.