Google Closure Compiler in JavaScript Released

[James Thornton]

Google released its JavaScript version of the Closure Compiler – "this allows Closure Compiler to run entirely in JS. Java is not required":

* https://github.com/google/closure-compiler-js
* https://developers.googleblog.com/2016/08/closure-compiler-in-javascript.html

Switching to the JS compiler means JS devs coming to ClojureScript will be able to use the tools they're familiar with a simplify the onboarding docs on the website.

I created a ticket here: http://dev.clojure.org/jira/browse/CLJS-1865

NB: I discovered this while experimenting with using ClojureScript with Polymer:

* https://medium.com/dev-channel/polymer-the-closure-compiler-e80dd249d9d7#.10xytauqf

* http://closuretools.blogspot.com/2016/06/using-polymer-with-closure-compiler-part-1.html

- James

[David Nolen]

Yes we are aware of this and we do not intend to pursue since it offers nothing in the way of real benefits.

It does seem potentially useful to third party efforts around bootstrapped ClojureScript, but that's about it.

David

- James

--
Note that posts from new members are moderated - please be patient with your first post.
---
You received this message because you are subscribed to the Google Groups "ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscribe@googlegroups.com.
To post to this group, send email to clojur...@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[mars0i]

On Tuesday, December 6, 2016 at 11:31:59 AM UTC-6, David Nolen wrote:
> Yes we are aware of this and we do not intend to pursue since it offers nothing in the way of real benefits.
>
>
> It does seem potentially useful to third party efforts around bootstrapped ClojureScript, but that's about it.

I don't have an understanding of the tradeoffs involved, but given the little bit of semantic and practical funkiness involved in macros being compiled in Clojure and run in Clojurescript, I would have thought that moving to an all Javascript/Clojurescript system could possibly be a good thing in the long run.

[David Nolen]

Macros are just a completely different topic from the original post. Separating the macro system from runtime means you don't have 2.5mb of JavaScript which can't be dead code eliminated when you start writing a simple client application.

David