I'm studying clojurescript/closure to better understand if using clojurescript could be really a step ahead in developing rich web based application. So, I'm still a newbie. I found in some way useful this google service http://closure-compiler.appspot.com/home to evaluate gclosure benefits form code reduction point of view.
In any case I think that the dead-code elimination is a great thing, but more importants, IMHO, are others two issues: a) resolving impedance mismatch between FP/UI (functional reactive programming? use macro to minimize incidental complexity in using OO UI?) b) clojurescript debugging I would never choose clojurescript on the client-side just to obtain a dead-code reduction (in any case it's a plus), but because it can reduce develoment time and increase robustness. Mimmo On Tuesday, September 18, 2012 4:03:29 PM UTC+2, Matt Campbell wrote: > > On 9/18/2012 8:57 AM, David Nolen wrote: > > I've heard of several large > > ClojureScript programs that generate 1.2-1.8 *megabytes* of > > JavaScript. After advanced compilation and gzipping the applications > > are around 40k-50k (http://blog.mezeske.com/?p=552). This is pretty > > impressive given that jQuery, which is pretty standard these days, > > itself is 32k gzipped. > > That is indeed impressive. I'd say the overhead of ClojureScript in > small programs is a non-issue then. Sorry for making a fuss about it. > > Matt > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
