> > It could be conditioned on jsinterop being switched on or not, in > general though, more and more compiler switch modes I think encourage > lazy/bad code practices in the ecosystem. >
Conditioned on jsinterop would really be bad, since all js wrapper libs will soon be based on jsinterop which makes that switch literally always on. IMHO any optimization that breaks java behavior should be optional and only explicit activated by a project's dev team because the dev team needs to know the implications of these optimizations. GWT needs to be very careful with such optimizations as most people choose GWT because they are not that familiar with JS and they expect that all java behaviors carry over to JS once the app is compiled and not just most of them. Back in the days I lost quite some time figuring out why a GWT-RPC request failed to serialize and it was because browsers had started using sub pixel coordinates and GWT has treated int, float, double the same which caused trouble in a serializer. In general I am fine with such optimizations but I would prefer if all such optimizations are turned off by default and there would be a chapter about optimizations in the documentation which describes the implications of such optimizations in more detail, especially for Java devs without lots of JS background knowledge. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a69f1163-f8a7-47ac-949e-0f1f84c1d793%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
