4 ms·

Nothing against Common Lisp but CL is not the lisp and it never will be. CL is a lisp same as Clojure - http://www.islisp.info/faq.html http://www.islisp.info/f

Nothing against Common Lisp but CL is not the lisp and it never will be. CL is a lisp same as Clojure - http://www.islisp.info/faq.html http://www.islisp.info/faq.html. Also you seem to have no problems critiquing a language which you obviously have no significant experience with - "Clojure is an experiment in STM". Guffaw.

hga 13y ago
As a historical example, mainline LISP prior to CL was dynamically scoped, something corrected in Scheme and adopted by CL a decade later, which, from my Maclisp and Lisp Machine Lisp background at the time was perhaps its biggest breaking change (very possibly not from the viewpoint of an Interlisp person).
lispm 13y ago
Clojure is a new language. Everything in Clojure had to be implemented new. There is zero compatibility and zero code sharing to/with Common Lisp, Emacs Lisp, Autolisp, ISLisp, Standard Lisp, Maclisp, Lisp Machine Lisp, ...
- hga 13y ago
  Which are all examples of mainline LISP. What about Scheme? Sure, it was bootstrapped in Maclisp, but not too long after had pretty much "zero compatibility and zero code sharing" with mainline LISPs. But is it not a LISP?
  - lispm 13y ago
    There are different types of Lisps. 1) the Lisps: they carry the name and share basics: Lisp 1.5 ... Common Lisp, ... 2) the derived dialects with some compatibility: Scheme, Interlisp, ... 3) the derived^2 dialects: Logo, MDL, Dylan, Racket, Clojure, ... 4) the derived^3 dialects: ML, ... The Lisps is category one were and are able to share code. Emacs Lisp implements some of Common Lisp. Something complex like the LOOP macro was once a single source file for Maclisp, Lisp Machine Lisp and Common Lisp. Clojure shares no source code with any other Lisp. It renames basic vocabulary ('atom') and lacks some older concepts. It's basically a new language.
- Mikera 13y ago
  One of the reasons that Clojure has so many libraries is that most things didn't have to be implemented from scratch. Building Clojure on the JVM was a genius move by Rich Hickey - it meant that an advanced runtime platform (the JVM) and a huge ready-to-use library ecosystem was already there from day 1. Backwards compatibility with Common Lisp was never a goal. The JVM ecosystem is bigger by far (and IMHO more valuable as a target).
mrottenkolber 13y ago
Actually I use Clojure professionally, and am very glad about it.

hga 13y ago

As a historical example, mainline LISP prior to CL was dynamically scoped, something corrected in Scheme and adopted by CL a decade later, which, from my Maclisp and Lisp Machine Lisp background at the time was perhaps its biggest breaking change (very possibly not from the viewpoint of an Interlisp person).

lispm 13y ago

Clojure is a new language. Everything in Clojure had to be implemented new. There is zero compatibility and zero code sharing to/with Common Lisp, Emacs Lisp, Autolisp, ISLisp, Standard Lisp, Maclisp, Lisp Machine Lisp, ...

hga 13y ago
Which are all examples of mainline LISP. What about Scheme? Sure, it was bootstrapped in Maclisp, but not too long after had pretty much "zero compatibility and zero code sharing" with mainline LISPs. But is it not a LISP?
- lispm 13y ago
  There are different types of Lisps. 1) the Lisps: they carry the name and share basics: Lisp 1.5 ... Common Lisp, ... 2) the derived dialects with some compatibility: Scheme, Interlisp, ... 3) the derived^2 dialects: Logo, MDL, Dylan, Racket, Clojure, ... 4) the derived^3 dialects: ML, ... The Lisps is category one were and are able to share code. Emacs Lisp implements some of Common Lisp. Something complex like the LOOP macro was once a single source file for Maclisp, Lisp Machine Lisp and Common Lisp. Clojure shares no source code with any other Lisp. It renames basic vocabulary ('atom') and lacks some older concepts. It's basically a new language.
Mikera 13y ago
One of the reasons that Clojure has so many libraries is that most things didn't have to be implemented from scratch. Building Clojure on the JVM was a genius move by Rich Hickey - it meant that an advanced runtime platform (the JVM) and a huge ready-to-use library ecosystem was already there from day 1. Backwards compatibility with Common Lisp was never a goal. The JVM ecosystem is bigger by far (and IMHO more valuable as a target).

mrottenkolber 13y ago

Actually I use Clojure professionally, and am very glad about it.