Path: utzoo!attcan!uunet!samsung!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!mimsy!mojo!SYSMGR@KING.ENG.UMD.EDU
From: sysmgr@KING.ENG.UMD.EDU (Doug Mohney)
Newsgroups: comp.arch
Subject: Re: Macintosh OS
Message-ID: <00937CC8.D7CCE7E0@KING.ENG.UMD.EDU>
Date: 6 Jun 90 19:19:23 GMT
References: <M0Y3WUE@xds13.ferranti.com> <1990Jun6.055847.14995@d.cs.okstate.edu>,<9548@pt.cs.cmu.edu>
Sender: news@eng.umd.edu (The News System)
Reply-To: sysmgr@KING.ENG.UMD.EDU (Doug Mohney)
Organization: The U. of MD, CP, CAD lab
Lines: 18

In article <9548@pt.cs.cmu.edu>, lindsay@MATHOM.GANDALF.CS.CMU.EDU (Donald Lindsay) writes:
>>  So the whole point is that any background app that hogs the CPU was
>>written irresponsibly, even though it may come from Apple. (MacWrite and
>>MacPaint both did naughty things!) 
>
>Hmmm. Several major products from Apple both did naughty things?
[ Other stuff cut...]
>.....  Nor does Apple: they do intend to eliminate this blemish.

MacPaint and MacWrite were written as quick and dirty applications to show
what the Mac is capable of, and were (probably, I don't know 100%) developed
before Apple's "Thou shall write apps to follow these standards." 

MacWrite got turned into MacWrite II, and I don't know what happend to
MacPaint; I think most people started using SuperPaint and lived happily
ever after. 

				Doug