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?) 28 нояб. 2016 г. 11:04 пользователь "Frank" <[email protected]> написал: > 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/ > topic/google-web-toolkit/IIQk4xH0-g8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- 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 protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
