Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: NeXT on Campus -- How's NeXT really doing at your school?
Message-ID: <1764@toaster.SFSU.EDU>
Date: 21 Jun 91 08:03:11 GMT
References: <lh5H?zbu@cs.psu.edu> <993@rosie.NeXT.COM>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 23

In article <993@rosie.NeXT.COM> mccoy@cory.berkeley.edu writes:
>and small lab purchases, but there aren't any large labs yet.  (Part of that  
>could be that the state of California and the UC system are in the middle of  
>big cutbacks to address the BIG deficit)

Frightening, that.  UC has *much* more money than the CSU.

>Also, I seem to recall that SF State's CS department has standardized on next.

Not really--it just so happens that NeXT provides the most cost-
effective way to meet *our* needs... and that has been
continuously true since Fall 1988.

"Our" needs may not be the same as "your" needs; for example,
we don't "need" X Windows...  (We have about half a dozen
platforms that support X, but it's not used in any sort of
"open" way--no client-and-server-on-different machines, and
hardly anyone even considers programming for it.  It runs xterm
and xclock, and a few "canned" packages.  On systems with both
X *and* a proprietary window system, users prefer the proprietary
package because it's invariably many times faster.)

					-=EPS=-