Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!sewilco@meccts.MECC.COM@hpda.UUCP
From: sewilco@meccts.MECC.COM@hpda.UUCP
Newsgroups: mod.computers.68k
Subject: Re: Multitasking at el...
Message-ID: <8702220030.AA27592@meccts.MECC.COM>
Date: Sun, 22-Feb-87 01:30:10 EST
Article-I.D.: meccts.8702220030.AA27592
Posted: Sun Feb 22 01:30:10 1987
Date-Received: Thu, 26-Feb-87 21:33:07 EST
References: <8702211138.AA05883@ucbvax.Berkeley.EDU>
Sender: mwm@ucbvax.BERKELEY.EDU
Reply-To: meccts!sewilco (Scot E. Wilcoxon)
Organization: Changing beyond limit of organizational domains.
Lines: 18
Approved: info-68k@ucbvax.berkeley.edu
Summary: Any abbreviations can be misinterpreted.  End of subject.

[stuff about MMUs, whether personal computers/workstations need MMUs]

In response to a repetition of the claim about odd UNIX command names,
I started to give alternative meanings to all the poster's MS-DOS
examples (ie, "type" shows file type or language).  Instead I'll just
point out that any terse command language requires training.

Icons and menus (a form of fill-in-the-blank) reduce the training.  But
if a text command language is needed, it must be more verbose to reduce
ambiguity.  Even natural English is too ambiguous.  Let's not bring
COBOL into this. :-)

Interface discussions belong in another newsgroup anyway.
---
Scot E. Wilcoxon   (guest account)  {ihnp4,amdahl,dayton}!meccts!sewilco
(612)825-2607           sewilco@MECC.COM            ihnp4!meccts!sewilco

	"...it don't snow in Minneapolis when the winter comes..."