There's no technical reason why not Java the language, but as for the infrastructure available for compiling Java to JavaScript and getting convenient bidirectional access to the JavaScript universe for use in a web application, there are more questions now.
Let's say you want to use GWT 2.8 and JsInterop with Polymer. You still have to use JSNI to instantiate JavaScript objects, but that's now discouraged because it will go away. Even when GWT 2.8 is released, the implementation of JsInterop itself will change if the GWT compiler is abandoned in favor of the transpiler. JsInterop annotations may then have to change again due to unforeseen circumstances, but that is speculation. Meanwhile, what do you do about RPC, or i18n, for example? You can push more and more functionality into JavaScript, but then you lose some of the benefits of Java. Anything that depends on gwt-user is to be avoided. There is a nice video suggesting what direction to take (https://www.youtube.com/watch?v=0flgI0AMJjk&index=8&list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE), but it's worth thinking through just how different applications will look that are written to these recommendations vs a standard GWT application today. On Friday, June 12, 2015 at 11:42:37 AM UTC+2, Alain wrote: > > Well the question could also be why not java ? > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
