Aucbvax.5223
fa.info-vax
utzoo!decvax!ucbvax!info-vax
Tue Nov 17 15:13:36 1981
learning to unix
>From RUBENSTEIN@HARV-10 Tue Nov 17 15:04:19 1981
Whoa, I knew I was opening a floodgate, but this is ridiculous...
Thanx to all the people who have told me about the "cat" command,
and thanx also to those who suggested that this information could
be had from "the manual."
Obviously, one way to learn about something is to read through
an encyclopedic reference manual and make notes on the things
that are useful. If there is an introductory manual which
introduces unix concepts and proceeds from basic to more
complicated commands, I'd love to hear about it -- I've never seen
one.
Obviously, I could probably learn unix on my own by reading
something or other, and I apologize to anyone who is annoyed
by people who use general mailing lists such as this for basic
queries that could be had from any manual (I am this way sometimes,
as are most folks who are knowledgable about anything, I daresay).
I didn't bring up the subject as a simple query for specific
information, but rather to illustrate a point which is exemplified
by my difficulty in typing out a file. "cat" is about as
non-obvious and non-mnemonic as you can get. If someone knows
about pipes and how unix defaults them, then it is obvious,
but such a person will already have been using "cat" for quite
some time. While I concede the possibility (even maybe the
probability) that unix is a real win for the sophisticated
user, no one can claim that it is straightforward for the
relatively inexperienced user to learn.
I realize that the system could be tailored for the inexperienced
user; I have used the same arguments that you are thinking up
at this very minute in justifying VMS, which I know very well.
However, I would much rather put cp:==copy in my
LOGIN.COM file than put copy:==cp in the default system login.
In the end, it probably makes little difference, but due
to thes defaults, a shell script is about as comprehensible
as a TECO macro, whereas a VMS COM file is usually fairly
understandable, if a bit awkward to write in the first place.
It is almost axiomatic that a very user-friendly system will
be found be completely obnoxious by the sophisticated user, but
I submit that it is this sophisticated user who knows best what
heesh wants, can best set things up that way, and will be using
the system enough to make it worth his while.
unix was obviously created by some \very/ sophisticated users, but
it's a shame that this creation can only be used by those of
(potentially, at least) equal stature.
Finally, I feel compelled to add that I suspect that I will fall in
love with unix as soon as I become proficient at it; it sounds
like something I would like (I'm a FORTH addict, too, remember; the
same arguments apply there as well). The power of the system is
not up for debate. If The Implementors are listening, take this
as a plea for a default user interface that is friendly, helpful,
verbose, and that comes with an off switch.
Stew
-----------------------------------------------------------------
gopher://quux.org/ conversion by John Goerzen <
[email protected]>
of
http://communication.ucsd.edu/A-News/
This Usenet Oldnews Archive
article may be copied and distributed freely, provided:
1. There is no money collected for the text(s) of the articles.
2. The following notice remains appended to each copy:
The Usenet Oldnews Archive: Compilation Copyright (C) 1981, 1996
Bruce Jones, Henry Spencer, David Wiseman.
