Though lisp provides a lot of syntactic flexibility. The beauty of lisp is in giving the programmer confidence that you can create a prototype extremely quickly and then optimize it when needed.
I find the hardest thing in the world is getting started. Once I start its never as hard as I thought it was going to be. In a nutshell, Lisp helps me get started and then lets me get the code ready for prime time.
If you are a web developer, I'd say spend a weekend trying out UCW, write a reddit clone in it. Then try to write it in python. It'll be obvious what lisp has to offer.
I'd start by reading SICP by Sussman and Abelson. Their lectures are available in video. I had a profound experience at the end of lecture 2b where they explain how car, cdr and cons are defined, thus explaining that in lisp, code is data.
The above comes with a warning... Lisp is truely the red pill. Once you've figured it out, you'll find it physically impossible to code in any other language.
Without knowing much about Lisp, it seems that trying to describe it is like to trying to tell someone about Buddhism, or Jazz. Talking about it is just not the same thing as "getting it".
Thanks for your thoughts vikram, If I do become a convert I'll be sure to make a special post to news.yc :)
This is what is often referred to as "Domain Specific Languages". With Lisp, you can create a DSL and its still Lisp.
That is what the article is saying, but much more verbosely. In the article's defense, I think it takes something as long as that for people who don't know Lisp to really understand the point.
It took me 3 read throughs of this article to begin to get a sense of what makes people rave about LISP. I've also read Chapter 2 of PG's book. From what I can see, I like.
I'm not saying I'm a convert (yet!) but I absolutely plan on reading Paul's book and working through the examples and excercises there.
In the meantime, is the article a good way to think about Lisp?