Linked by Thom Holwerda on Sat 28th Jul 2007 09:02 UTC, submitted by Kelly Rush
Thread beginning with comment 259127
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
A well-designed GUI presents a limited list of descriptively labeled relevant options (menus and buttons) whereas a CLI requires the user to know commands from memory. A GUI can use metaphors from real life, such as folders and arrows and pictures, whereas a CLI is just a blinking cursor. GUIs are a familiar concept to many users from machines in daily life such as ATMs and cell phones; CLIs are alien to most people. GUIs are for people who need ease of use rather than unlimited power, which is most people.






Member since:
2006-01-02
What's the real difference between a command-line interface and a GUI anyways? They both require the OS to present some sort of screen-based interface to the user. Whether it is pure text, or graphics is just a question of additional features. Input/output must still be multiplexed somehow and separated on a process by process basis. If the OS enforces access control and permissions on files, terminals, memory and CPU, why should it also not enforce access control and permissions on the shared resource that is the screen?