Timeline for Why are terminal consoles still used?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2016 at 14:08 | comment | added | DevSolar | Expert-friendliness vs. beginner-friendliness. | |
| Dec 8, 2016 at 18:56 | comment | added | anotherdave |
& to compliment this — often the computer is faster in CLI than the GUI too. E.g. moving a large directory structure can be much quicker with mv than dragging & dropping through Finder
|
|
| Dec 7, 2016 at 0:02 | comment | added | IT Bear | Great answer! I like how it points out that depending on the user/target market, and the task at hand, a CLI could actually have better UX than a GUI. Different tools for different jobs. If I need to copy a file from a network drive to my desktop, mouse & GUI all the way. But if I'm copying every file in a folder, except for the ones that are older or same size, excluding *.lnk and *.thumb files, to a folder on network drive, and want to see what files already in the network folder were not present in my original folder, CLI tools actually make that job easier. | |
| Dec 1, 2016 at 7:43 | comment | added | mtraceur |
This answer points at a big core of the positive UX components that TUI/CLI has that most GUI UX people have just missed. It's why people who've climbed the learning curve of vi-like controls have a vastly better experience using them than conventional interfaces, for example.
|
|
| Nov 30, 2016 at 19:37 | history | edited | DA01 | CC BY-SA 3.0 |
added 1179 characters in body
|
| Nov 30, 2016 at 19:06 | history | answered | DA01 | CC BY-SA 3.0 |