Re:The Axis Of Eval: Why I ignore Clojure
by ohyes on Monday September 20, 2010 @11:56AM
(#1709259)
It is the tight coupling of the terms that is doing the disservice.
It is a modern language. -> T.
It is a lisp. -> T.
However,
I only hear, 'It is a modern dialect of lisp,' when I am being told why I should switch from Scheme or CL to Clojure.
This is a non-argument (there is no spec for what a 'modern' language includes). It also has the implication that whatever I am using is in some way non-modern. (Which is an odd attribution for something which is actively developed and I do my daily coding in). Is Java modern? How about Python? Scala? Ruby? It seems like a weird non-category. When I boot up sbcl, it isn't like i'm programming in lisp 1.5.
New would be cool, or saying it has modern features, also good.
Gonna make a new spec for Common Lisp, Common Lisp the Ancient Language.
It is a modern language. -> T.
It is a lisp. -> T.
However, I only hear, 'It is a modern dialect of lisp,' when I am being told why I should switch from Scheme or CL to Clojure.
This is a non-argument (there is no spec for what a 'modern' language includes). It also has the implication that whatever I am using is in some way non-modern. (Which is an odd attribution for something which is actively developed and I do my daily coding in). Is Java modern? How about Python? Scala? Ruby? It seems like a weird non-category. When I boot up sbcl, it isn't like i'm programming in lisp 1.5.
New would be cool, or saying it has modern features, also good.
Gonna make a new spec for Common Lisp, Common Lisp the Ancient Language.