Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utah-cs.UUCP
Path: utzoo!utcs!lsuc!pesnta!hplabs!utah-cs!brownc
From: brownc@utah-cs.UUCP (Eric C. Brown)
Newsgroups: net.cse
Subject: Re: AT&T 6300 at UVM
Message-ID: <3344@utah-cs.UUCP>
Date: Sun, 19-May-85 16:12:09 EDT
Article-I.D.: utah-cs.3344
Posted: Sun May 19 16:12:09 1985
Date-Received: Mon, 20-May-85 19:13:17 EDT
References: <109@nvuxf.UUCP> <288@tilt.FUN>
Reply-To: brownc@utah-cs.UUCP (Eric C. Brown)
Organization: Univ of Utah CS Dept
Lines: 26
Summary: 

In article <288@tilt.FUN> chenr@tilt.UUCP (Ray Chen) writes:
>I think you underestimate the number of people who really USE
>computers.  I'm not talking about cpu cycles and disks alone, but also
>about tools and such available only in a Unix-style environment.
>
>The year I took the OS course, the final project was writing a
>stripped-down, multi-tasking, Unix-style kernel.  The next year
>I think it was a queuing simulation.  The compiler people write
>compilers.  My year we implemented a full Algol-style language
>(arrays, subroutines, scoping, the whole bit) in LISP.  This
>year, they're implementing a somewhat stripped down version of C
>using lex and yacc.
>

I think that you fail to understand the power of a 6300.  I use a Tandy
2000 (apx. 3x speed of IBM XT, 1.5x speed of 6300 or so), and I frequently
get better response time on C compilation and execution on the Tandy 2000 
than I do on a VAX 750.  Assuming the students are not running huge core
hogs like Lisp, I see no reason why software could not be developed on the
6300.  Every major tool that I have used on the VAX works on our Tandy 
(except Lex and Yacc, and those are available from the Austin Code Works,
but I haven't had a chance to order/evaluate them).

Eric C. Brown
brownc@utah-cs
{ihnp4, decvax, seismo}!utah-cs!brownc