Re:ClojureScript Is Not An Island: Integrating Node Modules
by prodtorok on Wednesday July 12, 2017 @06:33PM
(#14757243)
Amazing you consider an unstable, undecided, and hectic JavaScript world (language, 3rd party libraries, many competing tools, etc.) against the sanity of a singular language that has been stable and ahead of game since it's creation.
Re:ClojureScript Is Not An Island: Integrating Node Modules
by swannodette on Wednesday July 12, 2017 @06:02PM
(#14757069)
I fail to see how Closure Complier is any more complicated, more painful, and has any more caveats than Babel/Webpack. With Closure Compiler at 8 years old and building some of the most sophisticated JS properties on the web (GDocs anyone?) it seems pretty "solid" to me. Perhaps it not clear from the post but that's a big part of why this works, we're not doing the heavy lifting.
Re:ClojureScript Is Not An Island: Integrating Node Modules
by Scarbutt on Wednesday July 12, 2017 @06:18PM
(#14757169)
Its not about closure, is all the Clojurescript interop issues/gotchas, what's the correct way to do interop today in Clojurescript?
Re:ClojureScript Is Not An Island: Integrating Node Modules
by swannodette on Wednesday July 12, 2017 @06:22PM
(#14757189)
Nothing has changed about ClojureScript interop in 6 years so I don't really know what you're getting at. We believe ClojureScript interop is pretty good and our users pretty consistently agree.
Is passing through the complexity, pain and all the caveats one can encounter from this really worth it for using Clojurescript? Serious question, now that with have ES6+ and today babel/webpack are solid tools.
I mean from all the modules mess, I didn't get what's the correct way to do javascript interop right now.