Path: utzoo!attcan!uunet!cs.utexas.edu!ntvaxb!ac08
From: ac08@vaxb.acs.unt.edu (ac08@vaxb.acs.unt.edu (C. Irby))
Newsgroups: comp.arch
Subject: Re: Re^2: Macintosh OS
Message-ID: <26765.26701754@vaxb.acs.unt.edu>
Date: 8 Jun 90 21:23:32 GMT
References: <402@newave.UUCP> <3300131@m.cs.uiuc.edu> <5031@quanta.eng.ohio-state.edu> <1990May28.083518.26003@laguna.ccsf.caltech.edu> <54992@microsoft.UUCP> <12189@cbmvax.commodore.com> <355@three.MV.COM> <6570@scolex.sco.COM>
Lines: 20

In article <6570@scolex.sco.COM>, seanf@sco.COM (Sean Fagan) writes:
> In article <355@three.MV.COM> cory@three.MV.COM (Cory Kempf) writes:
>>A properly written user oriented program would check for events frequently, 
>>even in the middle of a heavy duty CPU burst.  That is just good user 
>>oriented development though.  Remember: The USER is in control.
> 
> And that is why the MacOS is not a "true" OS.  Because the *USER* (actually,
> the application) is in control, not the OS.
> 
>

Ohmigod!!!

Anything but THAT!!!

Once you let them user-types get in control, ANYTHING could happen!!!


;)
C Irby