An operating system that lacks a comprehensive command line is unmanageable. If someone comes up with a better (faster and/or more flexible) I/O mechanism than a text command line, I would be thrilled to use it.
The Windows & Mac GUI model is inadequate. Anything that can be done via GUI can be done faster via command line.
Command line is the only medium (other than the spoken word) I know of which uses the same language for input, processing, and output. That allows you to pipe output from one command into another command and use command output to specify the processing to occur.
Command scripts are organic things that can grow and adapt over time to address the needs of a specific system in a specific environment.
For diagnosing a problem, GUI isn't capable of being anything but second-best when compared to command line.
For speed of use, GUI isn't capable of being anything but second-best when compared to command line.
Thank you for your posting. This helped me to clairfy one of my arguments.
I submitted this twice as a slashdot article but it was refused both times.
The only way I could think of to get it posted anywhere on slashdot was to attach it to an existing Microsoft thread.
I sort of doubt many people will see it, though.
I have been asked to give a presentation to some Vice Presidents to help them understand specifically what admins don't like about Windows and why.
I've been a system admin for many years on many operating systems. I got talked into working for Microsoft as a contractor even though I think their operating systems are poorly designed.
I've given this a lot of thought over some years but would like to get additional input from other system admins who have been in the field for a long time (over 10 years) and have administered a variety of shared operating systems (e.g. both mainframes and fileservers).
I have a brief window of time in which to present our case and I don't want to leave anything out. Help me get them to understand! Specific facts and examples!"
Slashdot Mirror
An operating system that lacks a comprehensive command line is unmanageable. If someone comes up with a better (faster and/or more flexible) I/O mechanism than a text command line, I would be thrilled to use it. The Windows & Mac GUI model is inadequate. Anything that can be done via GUI can be done faster via command line. Command line is the only medium (other than the spoken word) I know of which uses the same language for input, processing, and output. That allows you to pipe output from one command into another command and use command output to specify the processing to occur. Command scripts are organic things that can grow and adapt over time to address the needs of a specific system in a specific environment. For diagnosing a problem, GUI isn't capable of being anything but second-best when compared to command line. For speed of use, GUI isn't capable of being anything but second-best when compared to command line. Thank you for your posting. This helped me to clairfy one of my arguments.
I submitted this twice as a slashdot article but it was refused both times. The only way I could think of to get it posted anywhere on slashdot was to attach it to an existing Microsoft thread. I sort of doubt many people will see it, though.
I've been a system admin for many years on many operating systems. I got talked into working for Microsoft as a contractor even though I think their operating systems are poorly designed.
I've given this a lot of thought over some years but would like to get additional input from other system admins who have been in the field for a long time (over 10 years) and have administered a variety of shared operating systems (e.g. both mainframes and fileservers).
I have a brief window of time in which to present our case and I don't want to leave anything out. Help me get them to understand! Specific facts and examples!"