Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac,comp.sys.amiga
Subject: Re: Mac Multitasking? (Silly expletive deleted)
Message-ID: <2793@hoptoad.uucp>
Date: Wed, 19-Aug-87 14:05:50 EDT
Article-I.D.: hoptoad.2793
Posted: Wed Aug 19 14:05:50 1987
Date-Received: Sat, 22-Aug-87 03:17:24 EDT
References: <8708191546.AA07324@cogsci.berkeley.edu>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Centram Systems, Berkeley
Lines: 16
Xref: mnetor comp.sys.mac:5727 comp.sys.amiga:7561

I would just loooove to explain the use of a task monitor and scheduling
priorities to the average Mac user, who sees the computer as a means to an
end, not an end in itself.  You really call this an advantage?  No wonder
the Amiga's not providing a serious challenge; ease of use for
non-technocrats is what counts today.

By the way, why hasn't anyone jumped all over the silly claim that
multitasking would get rid of event loops?  Event loops are an intrinsic
part of a modern graphical interface, as opposed to prompt-driven programs.
There are only two ways to program these interfaces: explicit event loops,
or a hidden (in the OS) event loop that calls event-handling routines
supplied by the programmer.  Either can be implemented with or without
multi-tasking, either pre-emptive or not.
-- 
Tim Maroney, {ihnp4,sun,well,ptsfa,lll-crg,frog}!hoptoad!tim (uucp)
hoptoad!tim@lll-crg (arpa)