Xref: utzoo comp.sys.atari.st:6664 comp.sys.amiga:12265
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!mike
From: mike@ames.arpa (Mike Smithwick)
Newsgroups: comp.sys.atari.st,comp.sys.amiga
Subject: Re: Multi-tasking? A nightmare...
Message-ID: <3782@ames.arpa>
Date: 29 Dec 87 17:01:46 GMT
References: <2027@bath63.ux63.bath.ac.uk>
Reply-To: mike@ames.UUCP (Mike Smithwick)
Distribution: na
Organization: NASA Ames Research Center, Moffett Field, Calif.
Lines: 37

In article <2027@bath63.ux63.bath.ac.uk> pes@ux63.bath.ac.uk (Smee) writes:
>
> [deleted a bunch of stuff on how "we really don't need multi-tasking"    
>
>I have an image of telling my machine 'make fred', and then letting it get on
>with it while I do a bit of word-processing, or whatever.  Only to be hit
>milliseconds later with an alert box:
>
>       BACKGROUND COMPILATION NEEDS LIBRARY DISK
>       PLEASE INSERT LIBRARY DISK INTO DRIVE B
>
>and, a second or two after I do that:
>
>       FOREGROUND PROCESS NEEDS AUTO-SAVE DISK
>       PLEASE INSERT DISK INTO DRIVE B
>
This reminds me of a joke. . .

   A guy goes to a doctor and says "Doc, it hurts when I do this" (he lifts
   an arm up, or something)

   So the doctor says, "well then, don't do that".

If running marble-madness slows up a compile too much, don't run 
marble-madness.

The moral of the story is, don't ask us do be limited by others "limitations".
As opposed to IBM, and now even (Cr)Apple, who are now bending down to the
lowest common denominator, who don't want to burden the average user with
unnecessary complexity (the original closed-Mac architecture was a 
manifestation of this philosophy).

-- 
				   *** mike (powered by M&Ms) smithwick ***
"if it wasn't for venitian blinds,   
it would be curtains for all of us!"
[discalimer : nope, I don't work for NASA, I take full blame for my ideas]