News for hackers. Stuff that matters.
Re:How Python is killing Lisp by mnemonicsloth on Saturday December 12, 2009 @09:25PM (#992274)
Three years old.

When this was written, there was no such thing as Clojure [1], and a number of now-essential CL libraries were just getting started.

Providing no new information, this article just invites needless soapboxing.

[1] Clojure is fast, free, trendy, inherently parallel, and fits seamlessly into the Java ecosystem. It's just an anecdote, but I notice less complaining about parentheses, too.

Re:How Python is killing Lisp by camccann on Saturday December 12, 2009 @11:43PM (#992423)
It's just an anecdote, but I notice less complaining about parentheses, too.

I still like the idea of "Lisp with syntactic whitespace". A few simple transformation rules to add implicit parentheses based on indentation would make it a lot more readable for people who aren't already veteran Smug Lisp Weenies.

There was even a specification written for adding it to Scheme: http://srfi.schemers.org/srfi-49/srfi-49.html

Re:How Python is killing Lisp by ynniv on Sunday December 13, 2009 @01:44PM (#992962)
It didn't feel needless when I wrote it. The lisp community was sitting on their haunches (their laurels had long rotted away), and silly new languages were stealing lisp's thunder. Today, I would probably have written about how clojure will soon be "killing" python, so maybe I'm just a soapboxer.
Re:How Python is killing Lisp by cema on Saturday December 12, 2009 @09:28PM (#992277)
You are correct. Still I think it offers useful historical perspective.
Re:How Python is killing Lisp by mnemonicsloth on Saturday December 12, 2009 @09:39PM (#992289)
Lisp already has too much historical perspective. That's one of the things people like about Clojure.