clojurescript

In ClojureScript these are written in Clojure or ClojureScript so there's really not as much to share as it would seem.

How does the output of the ClojureScript-compiler-in-ClojureScript compare to the real thing?

Once the ClojureScript is compiled to JavaScript, the JS can be executed by the browser (which of course involves an additional JIT compilation step).

I think the difference is that the Clojurescript community is really on the leading edge of web application development techniques.

This means that we'll still want to use the Java version of ClojureScript in most cases.

ClojureScript is now self-hosting, which means that you can eval any valid ClojureScript, so yes, eval in ClojureScript is now equivalent to the eval in languages like Clojure, Racket or any other Lisp.

The best way to think about this development is that it is a client-side compiler for ClojureScript.

He skipped Clojure and went straight to ClojureScript and has been having the time of his life.

One thing that's simpler in ClojureScript is that it only has one type of shared mutable reference, the Atom.

However, the Java version of the ClojureScript compiler can leverage Google's Closure Tools, which include a rather useful Javascript optimizer.

ClojureScript is probably not the best language to use if you want few layers of abstraction.

The JVM-based compiler will continue to be the best way to compile ClojureScript projects for production.

As alluded to in the post while I tend to do a lot of "driving" - this release was the result of a broader effort by the growing Clojure & ClojureScript communities.

Lisp in the browser has been much on my mind as I've been trying to get a handle on Clojurescript.

Clojurescript is a Lisp with dynamic typing, Elm/Purescript are ML dialects where (static) typing is much more important, in Purescript more so than Elm.

Here's an example of a repository that I've repurposed to compile both Clojure + Clojurescript.