Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!sdd.hp.com!wuarchive!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: Re^2: Term Progs
Message-ID: <16227@smoke.brl.mil>
Date: 22 May 91 01:47:09 GMT
References: <2436@novavax.UUCP> <1991May21.201141.10732@nevada.edu> <1991May21.215913.18781@utstat.uucp>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 12

In article <1991May21.215913.18781@utstat.uucp> philip@utstat.uucp (Philip McDunnough) writes:
>Make things simple, but provide powerful tools to those who need them.

What I recommend (coming from many years of studying UNIX) is that one
implement "computational kernels" as generally as possible, preferably
user-programmable, and ALSO provide a spiffy user interface that of
necessity hides a lot of the computation kernel capabilities as a
tradeoff for a simple-but-limited user model.  As with all UNIX
windowing systems in common use, one can then revert to an "expert"
environment that makes the computational kernel directly available, or
stick to a "naive user" environment that provides just the limited
user interface.