[ClojureScript] Re: Will advanced optimizations be officially supported on nodejs?

Thomas, Thank for you reply. The hello-world.core is from "Quick start" wiki page of clojurescript on github. With explicit :static-fns :optimize-constants and :optimizations :simple, there is no significant difference. Yes, the comparison was did on hello world program and is unfair indeed,

Re: [ClojureScript] Re: Will advanced optimizations be officially supported on nodejs?

在 2016年1月25日星期一 UTC+8下午6:15:44，Moe Aboulkheir写道： > On Mon, Jan 25, 2016 at 10:04 AM, Thomas Heller wrote: > Technically there is nothing holding you back from using :advanced on node, > IF you supply all externs that is. And this is where the problem lies, you > cannot easily

[ClojureScript] Re: Will advanced optimizations be officially supported on nodejs?

About the bug(or issue) I mentioned before on cljs.core.async/timeout. Several days ago, I have tried core.async and then got sucked... Google gave me two links: . "cljsbuild :simple optimization breaks cljs.core.async timeout on Node.js" [1] . "ASYNC-110 0.1.346, using >! crashes with no

[ClojureScript] Re: Will advanced optimizations be officially supported on nodejs?

Technically there is nothing holding you back from using :advanced on node, IF you supply all externs that is. And this is where the problem lies, you cannot easily provide externs since the closure compiler doesn't understand "require" properly. CloSure assumes there is one global namespace

Re: [ClojureScript] Re: Will advanced optimizations be officially supported on nodejs?

On Mon, Jan 25, 2016 at 10:04 AM, Thomas Heller wrote: > Technically there is nothing holding you back from using :advanced on > node, IF you supply all externs that is. And this is where the problem > lies, you cannot easily provide externs since the closure compiler