On Wednesday, November 26, 2014 9:09:58 AM UTC-6, Matthew Gertner wrote: > My colleague was complaining about waiting ~20 seconds for his ClojureScript > to compile and discovered this post on Stack Overflow: > http://stackoverflow.com/questions/20917202/auto-building-clojurescript-files-for-compojure-app. > In a nutshell, compilation time goes _way_ down if `optimization` is set to > `:none`, but some hackery is needed to get the resulting JS to run. (I didn't > check yet whether `:none` is a supported value or whether any unsupported > value would have the same effect.) > > Is there some option for turning off optimization completely that we haven't > been able to find? If not, is there some reason not to support this? Wouldn't > it be possible to adapt the parser so that it emits runnable JS without any > optimization at all during the dev process? The compilation time speedup is > really significant.
What you describe is exactly what ":optimization :none" does. It emits javascript generated by the clojurescript compiler *without* compiling that javascript with the google closure compiler. It requires different script elements in the html because the clojurescript compiler outputs one js file per cljs file, but the google closure compiler squashes it into one js file. There is a ticket[1] that has a proposal to simplify this so you can use the same html in both cases. [1]: http://dev.clojure.org/jira/browse/CLJS-851 -- 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+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
