Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!mailrus!iuvax!noose.ecn.purdue.edu!ei.ecn.purdue.edu!dev
From: dev@ei.ecn.purdue.edu (Larry Weeks)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Windows 3.0
Message-ID: <1990Jun28.224435.21026@ecn.purdue.edu>
Date: 28 Jun 90 22:44:35 GMT
References: <4085@uqcspe.cs.uq.oz.au> <1018@ashton.UUCP> <4100@uqcspe.cs.uq.oz.au> <1990Jun28.050337.7529@cunixf.cc.columbia.edu> <7671@fy.sei.cmu.edu>
Sender: news@ecn.purdue.edu (USENET news)
Organization: Purdue University Engineering Computer Network
Lines: 23

In article <7671@fy.sei.cmu.edu> bwb@sei.cmu.edu (Bruce Benson) writes:
>I once had a unix fanatic (NOT a guru) try to explain why my msdos PC
>could not really multitask.  However, he was having a hard time starting
>a Unix background process ('&') that did something meaningful and obvious. In
>the meantime I had started about 3 cube demos running under windows and
>asked him "you mean something like this?"  He stood there dumbfounded as I
>started a few more.  This wasn't quite fair, but the notion that a PC can't
>multitask (the *right* way) without Unix should have died years ago.

Granted, a PC can multi-task. The problem is, what it multi-tasks.
Unix for a PC, OK. OS/2, maybe OK (super MS-DOS, but still TOO like 
MS-DOS). But MS-DOS itself? Ick. Although Unix is older, at least it is
open enough to change. Not so primitive as MS-DOS running on a 
powerhorse 386 in 1990. Not a flame or anything, just a note on the
primitive state of our desktop PC operating system.

Larry Weeks
dev@ecn.purdue.edu
--
Larry Weeks         |"Take time to deliberate, but when the time for
Purdue University   | action has arrived, stop thinking and go in."
Astro. Engineering  | -- Napoleon Bonaparte 
dev@ecn.purdue.edu  |"Education is a journey, not a destination."