From: Wayne.Brown@altec.com
To: Hacksaw <hacksaw@hacksaw.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Not a typewriter
Date: Fri, 11 May 2001 18:18:36 -0500 [thread overview]
Message-ID: <86256A49.00800177.00@smtpnotes.altec.com> (raw)
On 05/11/2001 at 04:43:13 PM Hacksaw <hacksaw@hacksaw.org> wrote:
<snip>
>Well, I can't disagree. Unix's biggest turn off was the stupid command names.
>It's a big reason why Unixoid systems aren't more commonplace. I only learned
>it because I was stuck at a desk with a Wyse terminal. Otherwise I probably
>would have played with the Autocad machines more. Once I understood the
>basics, I understood the power of the system.
My first exposure to Unix came in 1987 when I was assigned to write a datacomm
package in C on a Unix (AIX) workstation the company had just bought. I was the
only one in our shop who knew C, and no one else there had ever dealt with Unix
either. (I had heard of Unix, but didn't know anything about it.) My training
consisted of my boss handing me the manuals and saying, "Figure it out." For
the first two weeks I absolutely HATED that system; nothing made sense, vi
seemed insane, and I was stumbling blindly through the documentation (I'd never
seen a permuted index before). Then suddenly something clicked, it all started
to make sense, and I fell in love with it. That's why I think it's so important
for people to learn the Unix mindset before trying to deal with Unix systems.
It's also why I have so little patience with people who don't have the patience
to work through the learning curve.
<snip>
>But first we need a better help system. The absolute most stupid convention of
>Unix is the man command. The fact that SCCS before, and now Bash usurp the
>keyword "help" is beyond the pale.
I guess we'll just have to agree to disagree, because we have exactly opposite
opinions on all this. I love the short, cryptic command names, and I think man
is the best help system ever devised. (The GNU Info system, however, is the
spawn of Satan. :-) In case you haven't guessed, I love vi, too, and use it
whenever possible. If Unix (or Linux) ever gets to the point of losing things
like this, I'll have no desire to use it.
Wayne
next reply other threads:[~2001-05-11 23:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 23:18 Wayne.Brown [this message]
2001-05-14 22:22 ` Not a typewriter Kai Henningsen
-- strict thread matches above, loose matches on Subject: below --
2001-05-14 2:59 Wayne.Brown
2001-05-11 23:57 Bingner Sam J. Contractor RSIS
2001-05-11 18:37 Wayne.Brown
2001-05-11 16:07 Wayne.Brown
2001-05-11 17:03 ` Joel Jaeggli
2001-05-11 21:43 ` Hacksaw
2001-05-13 23:39 ` Mike A. Harris
2001-05-12 4:18 ` John Alvord
2001-05-13 23:35 ` Mike A. Harris
2001-05-14 1:03 ` Horst von Brand
2001-05-14 14:31 ` John Kodis
2001-05-14 15:25 ` Michael Meissner
2001-05-14 17:01 ` Alan Cox
2001-05-14 17:16 ` Michael Meissner
2001-05-14 17:29 ` Jesse Pollard
2001-05-14 18:04 ` H. Peter Anvin
2001-05-14 1:31 ` Jonathan Lundell
2001-05-10 23:06 Wayne.Brown
2001-05-10 23:20 ` Hacksaw
2001-05-10 23:52 ` Jonathan Lundell
2001-05-11 0:07 ` Alexander Viro
2001-05-11 2:01 ` Jonathan Lundell
2001-05-11 9:21 ` Malcolm Beattie
2001-05-11 0:10 ` H. Peter Anvin
2001-05-11 1:31 ` David S. Miller
2001-05-11 1:32 ` Blue Lang
2001-05-11 9:31 ` Alan Cox
2001-05-11 12:25 ` Richard B. Johnson
2001-05-11 9:37 ` Alan Cox
2001-05-15 14:01 ` Anuradha Ratnaweera
2001-05-10 21:42 Richard B. Johnson
2001-05-10 22:38 ` H. Peter Anvin
2001-05-11 7:22 ` Tom Leete
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86256A49.00800177.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=hacksaw@hacksaw.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox