🚀 go-pugleaf

Yes it's true, MPW for straight Pascal or C development is a total
crock.  What you gain in the flexibility of the evironment
(programmable editor, the MPW "tools" etc tec) really isn't worth the
loss in speed and convenience.

BUT, there is one very overpowering reason to put up with it all, and
that is, MacApp.  No other development system has it, and no other
Pascal compiler compiles it, and boy is it nice.

Of course, using it doubles your compile-link-edit time, and adds a
LOT of code to your application, and it takes up another 2 Meg on your
hard disk, but if you are developing BIG, compilcated applications
that need to have a great user interface, Macapp is great.  Like, to
get a simple program with DAs, printing and scrollable windows (in
both directions), you just plug in a few routines to set up and
display whatever data structures the program manipulates, compile
away, make a few library calls, and boom, it's done. No muss, no fuss,
and it's really that easy.

So, that's why I'd use MPW.  But, I'd only like using MPW on a Mac II
with a big disk...Mac II's are fast enough to make MPW not quite so
slow. 

Now, if those Think folks could add a bit of Objectness to their
C/Pascal compilers...well, THEN we'd have something.


Cheers,
Pete
-- 
ARPA: hugo@gnome.cs.cmu.edu      BELL:412-681-7431
UUCP: ...!{ucbvax,ihnp4,cmucspt}!hugo@gnome.cs.cmu.edu
USPS: 5170 Beeler St., Pittsburgh PA 15213

	"There are reports that many executives make their decisions by
	 flipping coins or by throwing darts, etc.  It is also rumored that 
	 some college professors prepare their grades on such a basis."
				- Donald Knuth