Newsgroups: comp.lang.dylan,comp.lang.lisp,comp.lang.lisp.mcl
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!usenet.eel.ufl.edu!news-feed-1.peachnet.edu!gatech!swrinde!pipex!dircon!rheged!simon
From: simon@rheged.dircon.co.uk (Simon Brooke)
Subject: Re: A Dylan implemented on Common Lisp
Message-ID: <D5I07t.2ts@rheged.dircon.co.uk>
Organization: none. Disorganization: total.
References: <2877601102@hoult.actrix.gen.nz> <D577F5.1H7@cogsci.ed.ac.uk> <D584q4.2E8@cee.hw.ac.uk> <D58KBE.s0@cogsci.ed.ac.uk>
Date: Wed, 15 Mar 1995 20:14:15 GMT
Lines: 23
Xref: glinda.oz.cs.cmu.edu comp.lang.dylan:3752 comp.lang.lisp:17098 comp.lang.lisp.mcl:6650

In article <D58KBE.s0@cogsci.ed.ac.uk>, Jeff Dalton <jeff@aiai.ed.ac.uk> wrote:
>In article <D584q4.2E8@cee.hw.ac.uk> andrew@cee.hw.ac.uk (Andrew Dinn) writes:
>>
>>I can attack Common Lisp without defending Dylan.
>
>I can attack Common Lisp too.  Indeed, there are many things I
>would rather were different.

Guys, we can *all* attack Common LISP; I've been doing it noisily for
years. But even I have at last come to the conclusion that if we kill
Common LISP now, we've probably killed LisP for all real world
commercial purposes. If you're happy to do that I can't stop you.

But I'd counsel you not, at least until we've got something which
suits us *as LisP hackers* to replace it with. Perhaps Dylan will be
that thing, but I'm suspicious of anything which moves *away* from
LisP syntax with the idea of making things better.

Simon
-- 
------- simon@rheged.dircon.co.uk (Simon Brooke)

	'graveyards are full of indispensable people'
