Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!udel!burdvax!sdcrdcf!sdcsmb!exec!darrelj
From: darrelj@exec.sm.unisys.com (Darrel VanBuer)
Newsgroups: comp.lang.lisp
Subject: Re: Ada,Lisp,Flames
Message-ID: <10@exec.sm.unisys.com>
Date: 29 Jan 88 00:16:21 GMT
References: <5084@well.UUCP>
Reply-To: darrelj@exec.sm.unisys.com (Darrel VanBuer)
Organization: Unisys Santa Monica
Lines: 22

In article <5084@well.UUCP> jjacobs@well.UUCP (Jeffrey Jacobs) writes:
>In <5174X@utah-cs.UUCP>, my good friend Stan Shebs writes:
>
>6.  Xerox Common Lisp.  MIA (Missing In Action).  Apparently still
>not ready to release.  **Rumor** has it that Xerox will abandon
>CL running on their own hardware and OEM Sun Sparc architecture
>running one of the above.  (Repeat;  **rumor**).
>
Xerox Common Lisp is out, and has been for a few months.  Deliveries
have been slow because of the magnitude of changes, and Xerox has
apparently trying to minimize the number of customers on the steep
part of the learning curve at one time.  Beta testing went faster than
planned because of the relative solidity of the job.  The main
weakness of what was delivered in the first release is that many of the
Interlisp tools don't grok common lisp yet (e.g. Masterscope).  It
does seem that Sun and Xerox have agreed in principle to migrate Xerox
software to Sun hardware (with Sun committed to support for XNS), but
indications are in products for a couple of years out.  I guess Xerox
finally decided their application customer base is too small to
support competitive hardware development (the Star/Viewpoint text
processing software is also migrating.  A year was a long time to be
overdue, though.