[jb1991]

Virding's YouTube presentation at a Clojure conference about this new lisp says this in the caption:

>LFE (Lisp Flavoured Erlang) has been designed to run efficiently on the Erlang VM and at the same time be a "real lisp" providing Lisp's good bits.

It also knocks Clojure a bit. What do you all think are the "good bits" of lisp that Clojure lacks?

[ska]

   What do you all think are the "good bits" of lisp that Clojure lacks?

Compared to common lisp off the top of my head (correct me if I am misrepresenting Clojure from memory): condition system, multiple return values and &key, CLOS with all that entails, and I seem to remember that clojure had some fiddly issues with macros and reader macros.

Not intended as a knock on Clojure, btw, but the JVM is somewhat limiting, in the same way you can't do a "proper" common lisp on the CLR.

[kaeluka]

FWIW, reading this sentence w/o any extra context, it doesn't seem to imply anything bad about clojure.

[hellofunk]

The bit about Clojure was additional information in the source that I did not quote.

[eggy]

Readable stack traces. Unfortunately, the JVM is the culprit here. I like Clojure's syntax, and some other bits, but if I were to chose a Lisp that runs under another system like Clojure, I'd choose Shen [1].

   [1]  http://shenlanguage.org/

[hellofunk]

>The Shen kernel is under BSD and currently runs under CLisp, SBCL, Clojure, Scheme, Ruby, Python, the JVM, Haskell and Javascript.

Hm, I guess I can't imagine how that would work, one language running under all those environments?

[jarcane]

Shen is built on it's own simplified parent dialect that is easily implementable in pretty much any language. Once you implement that core, everything else comes along for free, in theory.

[yurrriq]

Tail recursion optimization, for one. Clojure makes up for it with recur though, so in practice, it's not that big of a deal.