14 comments

[ 2.7 ms ] story [ 42.0 ms ] thread
TL;DR:

1. Lumo runs ClojureScript without the need for a JVM. It relies on Node.js and Google V8.

2. ClojureScript compiler is self-hosted, thus:

3. Now you can compile ClojureScript without the need for a JVM. As a bonus, enjoy shorter start-up times.

I think the article was saying that the javascript version of the google closure library is slower than the jvm based version so this would actually be a little bit slower.

Further, it has a serious restriction in that the version of cljs used by lumo itself is now the version of cljs that your project must use.

The cljs version is a pretty serious caveat but this seems like a really nice milestone on quite a bit of work. kudos to anmonteiro

ClojureScript compiles to JavaScript doesn't it? And isn't ClojureScript written in ClojureScript? So why would you need a JVM in the first place? What is new?
Google Closure Compiler being available to JS is relatively new. That was previously a JVM only ability.
Why do you need Closure though? If ClojureScript's compiler compiles to JS, why do you need Closure? You already have JS code and can already run it.
ClojureScript relies on closure compiler for dead code elimination.
I love this! Cljs has seen some huge leaps recently! I hope the momentum keeps building. Expo + Clojurescript is the stuff of dreams!
So could we make a Webpack loader form this?