🚀 go-pugleaf

In article <danpop.807285117@rscernix>, Dan.Pop@mail.cern.ch (Dan Pop) wrote:

 
> It ain't possible for the Mac, either.  That's why there are so many
> prosperous businesses in the Mac courses field.  Don't tell me you
> didn't need a Mac course, 'cause I didn't need a Unix course, either.

It is possible to sit down, see a menu, read "Print" and think, "hey,
maybe that prints a page.  It, however, is impossible to sit down, see

?

and think, "hey, maybe typing lpr (or lp depending on your type of Unix)
<filename> prints <filename>."

With a Mac, all the commands are in the menus.  With Unix, all the
commands are in the manual, man pages, or some 3rd party book.  Now I will
admit that there is money to be made in Mac classes, but it is nowhere
near as necessary as for Unix.  In Unix, you have to read something in
order to find out what the commands are.  On a Mac all the commands are
staring you straight in the face.
Also with Mac manuals, about the only use is for hidden commands such as
the dreaded startup key combinations and the really complex commands.  But
for less common, non-beginner things the manuals are more necessary.  It's
just that they aren't necessary to start.  And they're nowhere near as
necessary as a Unix manual or a good Unix book.  The same goes for DOS and
any other CLIs.

--
Hotel California
hotelca@cris.com