Xref: utzoo comp.sys.mac.programmer:3000 comp.sys.mac:22343
Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!elroy!aero!sm.unisys.com!csun!polyslo!dorourke
From: dorourke@polyslo.CalPoly.EDU (David M. O'Rourke)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac
Subject: Re: Inside Mac
Message-ID: <5261@polyslo.CalPoly.EDU>
Date: 1 Nov 88 18:19:25 GMT
References: <975@cps3xx.UUCP> <1282@tmpmbx.UUCP>
Reply-To: dorourke@polyslo.UUCP (David M. O'Rourke)
Organization: Cal Poly State University -- San Luis Obispo
Lines: 18

In article <1282@tmpmbx.UUCP> pengo@tmpmbx.UUCP (Hans H. Huebner) writes:
>My major complaint about the Mac is the bad documentation.  A better scheme
>could be helpful in getting rid of the prejudice that the Mac is hard to
>program.

   I wouldn't call the macintosh's documentation bad!  In fact compared to
most of the other windowing systems that I've seen {MS-Windows, X, & NeWS}
I'd say that it's quite good!  And the prejudice that the Mac's hard to 
program is also found in other windowing systems as well.
Most programmers aren't used to event driven programming and it takes quite a
bit to make the mind shift necessary to do it effectivly.  But to call
the Mac's documentation "bad" is inappropriate in my opinion.

p.s. That's not to say it couldn't be improved upon ;-)
-- 
David M. O'Rourke                                  dorourke@polyslo.calpoly.edu

"If it doesn't do Windows, then it's not a computer!!!"
Disclaimer: I don't represent the school.  All opinions are mine!