I have some glue. Google JS Compiler used in chrome is able to detect some patterns and jit. But some patterns are not detected.
Ex: for are deceted, do ... while sometimes not.
It happens so that GWT produce patterns detectable for JS Compiler. And Closure can break that structure.
I am happy that GWT dropped cl suppert and focus on JsInterop (where is JsIndexer?)
I am also interested in answers to this question.--
When Closure became available in GWT I did many real world tests on real world projects. And in the end the code compiled with closure was slower in every case (although smaller). So I never understood why anyone would want to use that closure compile on top of gwt compile.
Op donderdag 24 november 2016 15:05:50 UTC+1 schreef Kirill Prazdnikov:Do you have performance measurements ?Did the performance better for 2.7 ?Did you measured real transfer traffic (web server supports real-time GZ compression over HTTP) ?Thanks
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+
To post to this group, send email to google-web-toolkit@
Visit this group at https://groups.google.com/
For more options, visit https://groups.google.com/d/
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.