Xref: utzoo comp.sys.mac:44980 comp.sys.next:4513
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.mac,comp.sys.next
Subject: Re: The NeXT and the Mac
Message-ID: <9138@cbmvax.commodore.com>
Date: 22 Dec 89 07:15:06 GMT
References: <5094@blake.acs.washington.edu>
Organization: Commodore, West Chester, PA
Lines: 23

in article <5094@blake.acs.washington.edu>, mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) says:
> Xref: cbmvax comp.sys.mac:48060 comp.sys.next:4581

> The NeXT has real memory management and real multi-processing.  You
> cannot call MultiFinder "multi-processing."  

Actually, you can't call the NeXT "multi-processing" yet either, though of
course Mach supports multi-processing.  But, unless you count running the
68030 at the same time as the 56000, you're single processing on any NeXT
that NeXT is currently talking about.  

However, you are really multitasking.  With friendly applications on the
Mac, you're really multitasking too.  The big difference with a system
like the NeXT, designed for multitasking (like all UNIXs), is that you never
waste CPU time sitting in a task that's waiting for some external event,
while you certainly can under Multifinder.  And of course, you've got
real IPC on the NeXT.

> Mark Crispin / 6158 Lariat Loop NE / Bainbridge Island, WA 98110-2098
-- 
Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
                    Too much of everything is just enough