Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

DR-DOS, Plan, BSD, Sun Solaris, HP/UX, OpenServer.....and so on.

Why high-tech OSs (like UNIX family) are mostly command based (rather than GUI based)?

share|improve this question

migrated from stackoverflow.com Nov 28 '11 at 16:31

This question came from our site for professional and enthusiast programmers.

closed as off topic by Mark Trapp Nov 28 '11 at 16:39

Questions on Programmers Stack Exchange are expected to relate to software development within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

    
also I believe this question place is programmers of servers.stack –  alonisser Nov 28 '11 at 12:29
2  
Are you implying that other OSs are low tech ? –  Nasreddine Nov 28 '11 at 16:08
    
I'm not sure why this was migrated here, but speculating about design decisions for operating systems isn't really a topic about software development, and it's really not clear what distinction you're trying to make. –  user8 Nov 28 '11 at 16:39
add comment

4 Answers 4

  1. GUI is more difficult to build than CLI (command line interface).
  2. CLI is easier to agree on standards, as it's much simpler.
  3. GUI requires a graphical subsystem (more hardware and software components on servers which don't need it at all).
  4. CLI is easier to automate (scripts), simplifies administration.
  5. CLI allows express much more commands than GUI. E.g. my linux has 3500 commands, each of them has a lot of parameters. Do you imagine how complex the GUI would be? Much more complex than Microsoft Word.
  6. Less traffic to transfer when you need manage remote servers (more responsive on slow networks).
  7. Easier to communicate about CLI commands than buttons/menus/inputs/etc. Much more easier to send a command line text than bunch of screenshots.
  8. CLI allows compose commands easier. So you could an output from one command feed into an another command, and usually it works out-of-box. For GUI one thing is only clipboard, and maybe some technologies as OLE, ActiveX, etc, it works much worse than simple CLI text passing.
share|improve this answer
add comment

Try explaining in an email, or by phone, how to interact with a GUI.

Try explaining in an email, or by phone, how to interact with a command line. It is considerably easier: you could copy & paste the command inside the email.

(Variant, try to explain by email or by phone how to lace your tie or your boots)

Our brains work well on languages, including textual formal ones like command lines.

share|improve this answer
add comment

I'd say that it's because they expect their users to invest the time and resources it takes to learn the command line. After that, the command line gives you power to express actions, which may be much more time-consuming with a GUI (e.g. "change all users with email from "@domain.com" to inactive"). A bash prompt is much faster than a mouse, when you know how to use it.

share|improve this answer
add comment

Agree with Vladislav, the use of the command line gives the administrator the power to do almost everything, the only problem with the commands are that you have to know them and the GUIs are much more Instinctive, but most of the time you have to navigate throw windows to reproduce a simple command line...

After you know the commands, its really practical to use them...

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.