Hacker News new | past | comments | ask | show | jobs | submit login
Clojure is not a Lisp [2009] (imagine27.com)
2 points by willismichael on April 26, 2013 | hide | past | favorite | 3 comments



I still don't understand why Clojure isn't a Lisp. Because it's built on the JVM? Because it encourages using immutable data structures? Because it's becoming popular? Someone point out the key paragraph I missed connecting "Clojure is imperfect and hyped" to "Clojure is not a Lisp".


I haven't read the article, but when I say, in a certain context, that I don't consider clojure a Lisp, what I might mean is that clojure is not descendant from the original McCarty lisp. You can trace Common Lisps or Emacs Lisps roots from MACLISP back to that. In such a context where the definition of "lisp" is sufficiently narrow, I might call languages like clojure and scheme "lisp like languages", or "distant dialects".

It isn't any different from saying Linux is not Unix, but the various BSDs are. It doesn't really matter at all, and when used in the wrong context, such phrases can be confusing.


Clojure is not compatible with Lisp. It's a new Lisp dialect. Just like Logo, Dylan and a few others.

Common Lisp is the successor to Maclisp, which came out of McCarthy's Lisp. Thus you can port most old code to Common Lisp without much pain.

When people switched from Maclisp to Common Lisp, they patched their code. For some time the same code base ran in different dialects.

If you switch from Common Lisp to Clojure, you can rewrite everything or even just forget it anyway.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: