Re: command line vs gui

From: notbob (notbob_at_nothome.com)
Date: 11/16/05 

Date: Wed, 16 Nov 2005 11:06:38 -0600

On 2005-11-16, silicono2@yahoo.com <silicono2@yahoo.com> wrote:
> I've had a Unix-using acquaintance tell me that he much preferred
> command lines over GUI, even when using Windows. For all the advantages
> of GUI I agree that it's much easier to issue a series of commands in a
> command line or do something like "copy *.* a:" as well. Can we get the
> best of both worlds with an interface using charts/fields of text?

I remember the very first time I saw a 1st gen MacIntosh. The friend
who had one proudly put the keyboard out of reach and proceeded to
astound me for several hrs with all the things he could accomplish on
the little box with just that little "mouse" thingie. I was truly
amazed. But, years later, the other side of the coin was painfully
revealed when our company changed from a Unix based shell database to
Windows based Oracle. It was absolute Hell.

For me, it breaks down into not gui vs cli, but mouse vs keyboard. I
see no difference between selecting a highligthed/colored curses/shell
field and a graphic icon. Both are similar in the mental process. A
cli command is a series of carefully constructed txt options. A gui
is a series of carefully chosen ...more often than not, text!...
graphic options. The question is, which is faster and/or requires
the least effort. For me, a longime touch typist, the keyboard is
infinitely more efficient.

While I consider the mouse a necessary input device, I loath to reach
for the damned thing. It's a major pain to take my whole
hand/wrist/arm away from it's rested/supported position at the
keyboard and reach over and grab a hunk of plastic when I can just
extend a pinky and execute a couple taps. But, the mouse is
irreplaceable in certain applications. How can a keyboard easily
create a diagonal line? It can't. So, it depends on what one is
doing on the computer.

As a professional CAD user, I realize both the keyboard and the mouse
are invaluble input devices. In this primarily graphic environment,
the mouse is not only king, it's irreplaceable. I can do without the
keyboard, but not the mouse. OTOH, the mouse is still a lousy choice
for most input functions, even in CAD. Much quicker to tap a single
key under a well place finger than drag a cursor clear across a screen
to reach a bar full of icons. Even worse is having one hand
constantly going back and forth from the keybd to the mouse.

After more than a couple bouts with Repeated Strain Injury (RSI), I
finally settled on a very efficient and low physical impact solution
for CAD. A one handed keyboard (left) and a really good mouse. No
kidding! Neither hand need leave their respective device. Keyboard
for one or two tap command input and mouse for spacial graphics input.
It worked like a charm and my RSI probs disappeared.

But, back in the real non-CAD world, I still prefer the keyboard and
have reverted over the years back to as many CLI based applications as
I can get away with. I also prefer keyboard shorcuts in windows based
environments if they don't require too many keystrokes. I imagine
this would not be the case with someone who was not a proficient
typist. Also, I suspect there's another less obvious reason for the
overwhelming popularity of gui. The CLI requires the user actually
know a command and have it committed to memory. A gui typically
provides clues and/or prompts. It's like taking a test and really
knowing the answer to the question versus taking a multiple choice
test.

nb

Relevant Pages

  • Re: Win98 -- all kidding aside
    ... available to me through the GUI, ... the command line will always ... give the greater power and flexibility for certain tasks. ... things than Windows. ...
    (Ubuntu)
  • Re: Cobol books & experiences
    ... they are enthused about the command line? ... criticism of MicroSoft for trying to get us to work in a totally Windows ... even when debugging GUI code? ... that so often THEY forgot to put sufficient gas into that small generator. ...
    (comp.lang.cobol)
  • Re: Lost XP product key - before install.
    ... Windows it's amazing Linux doesn't have more of a market share. ... much faster than any GUI. ... > keyboard are needed. ...
    (uk.comp.homebuilt)
  • Re: HD Backup ?
    ... You do know you can add command line switches if needed to shortcut icons, ... one of my major gripes with GUI's & especially GUI ... Or in the case of Windows, even where to begin looking for the ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: good, reliable window manager?
    ... >> presented itself with a GUI. ... A GUI does not preclude keyboard control. ... to the command window, complete with its input and output history intact, ... and completion features of the shell that you were using. ...
    (comp.unix.bsd.freebsd.misc)
Loading