Lisp is Sin
- From: Adam Connor <ufo@xxxxxxxxxx>
- Date: Mon, 16 Jan 2006 09:39:19 -0600
Just a post I saw that I thought was interesting:
http://blogs.msdn.com/sriram/archive/2006/01/15/lisp_is_sin.aspx
Thinking about my response to this essay (and many others I've seen in
the last year or so), I would put it this way: Lisp has convinced many
people of its beauty and power, but has convinced few of its
practicality as a primary development tool for the here and now. I
guess you could look at that glass as being half-full or half-empty.
Where I work, I think it is more likely that we will add Ruby to the
toolkit than Lisp, mostly because
1) it appears to be easier for average developers to get started in
Ruby
2) the price is right; as a non-profit institution, commercial Lisps
seem kind of expensive.
3) the general consensus is that the Ruby community is friendlier and
more likely to offer constructive help.
That makes me sad, since I like Lisp, but I have to admit that I agree
with all three points. Am I missing some compelling counter-argument?
All roads may lead to Lisp, but maybe not any existing Lisp.
--
adamnospamaustin.rr.com
s/nospam/c\./
.
- Follow-Ups:
- Re: Lisp is Sin
- From: Nathan Baum
- Re: Lisp is Sin
- From: Kenny Tilton
- Re: Lisp is Sin
- From: Majorinc , Kazimir
- Re: Lisp is Sin
- From: Paolo Amoroso
- Re: Lisp is Sin
- From: Alan Crowe
- Re: Lisp is Sin
- From: jayessay
- Re: Lisp is Sin
- From: Joe Marshall
- Re: Lisp is Sin
- From: Cameron MacKinnon
- Re: Lisp is Sin
- From: Wade Humeniuk
- Re: Lisp is Sin
- From: Pascal Costanza
- Re: Lisp is Sin
- Prev by Date: Re: Another Lisp logo
- Next by Date: Re: Lisp and low-level operating system development
- Previous by thread: Re: Another Lisp logo
- Next by thread: Re: Lisp is Sin
- Index(es):
Relevant Pages
|
Loading