friendly messages

[Barry Shein]

>The result is a much cleaner interface; users know how to invoke
>programs, how to get help while using them, and how to interpret the
>messages they produce.  Sounds to me like a big win over the current
>state of affairs in the UNIX world.  The sooner we implement something
>similar, the sooner we'll be taken seriously in the real world where
>people run applications rather than hack software.
>
>Patrick Curran (uunet!ism780c!patrick)

You miss the whole point of Unix's terseness.

The point is that the output of one command is intended to be useful
as the input of another command, or, the terminal.

It's not a "user-friendly" issue or decision, it's a productivity
decision.  VMS doesn't have pipes and often produces output its other
programs can't read anyhow, due to the zillions of RMS file format
mismatches (even if you manage to figure out how to save it to a file,
no I/O redirection) so it's comparing apples and oranges, who cares if
it's full of "RMS-I-EVERYTHING-A-OK" messages, it's just zipping off
the screen anyhow (no piping to "more" either, lovely, user-friendly
system, zip zip zip...what was that?) It's nice to hear there's some
way to shut it up but that really begs the point (ie. the design of
VMS.)

Being as VMS never considered the output of its programs very useful
they felt free to babble whatever they wanted and generally make it
impossible to ever parse up.  In unix the designers preferred the
output of programs to be useful.

I realize people find this point aggravatingly subtle.

	-Barry "Keen Eye for the Obvious" Shein, ||Encore||