Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!houxm!houxz!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver (info-mac)
Newsgroups: fa.info-mac
Subject: Multitasking...
Message-ID: <1459@uw-beaver>
Date: Mon, 13-Aug-84 14:50:48 EDT
Article-I.D.: uw-beave.1459
Posted: Mon Aug 13 14:50:48 1984
Date-Received: Tue, 14-Aug-84 04:58:16 EDT
Sender: daemon@uw-beave
Organization: U of Washington Computer Science
Lines: 24

From: Nicholas.Caruso@CMU-CS-SPICE
I said multitasking, not multiprocessing.  It would be nice to have the
mac allow multiple tasks even if only one could be processed at a time-
it would allow a lot of neat things, like moving from macterm to a
spreadsheet, doing some calculations, cutting them, going back to macterm
and sending them to the remote listener (host, other mac, whatever).
All without exiting the current program.  This will necessitate large
memory and a *fast* hard disk...

Perhaps there could be a foreground task and a background task, the
latter not having a menu bar...  

I feel there are serious deficiencies in the present mac- including the 
rigidity of the user interface, and the total (from my position) lack of
development software running on a single mac, the near-impossibility of
obtaining a copy of the operating system documentation, the problem with 
memory expansion, ..., ..., ...

If the mac is to be sold as a "business computer" these may not be flaws
at all;  right now the mac is a machine that "could be" a very nice little
powerful personal computer.

                -Nick (rael@spice)