On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote: > > > My worry about "just pick a mainstream JS framework and use it via > JSInterop" is that if you're a) coupled to a JS environment for unit > testing and b) interfacing with a framework that is inherently > dynamic/untyped, what's the benefit of using GWT in the first place? >
And this for me sums up GWTs main issues going forward. The benefit before was that existing Java devs could use GWT to work on all the layers of an application. GWT 3 will force (not a bad thing) Java devs to use JavaScript for their views and will also force them to deal with integrating JS and Java code. At this point, you have to ask 'Why bother with Java/GWT at all' - switch the full application to pure JS. For existing large projects, switching to GWT 3 is almost a non-starter as there will be far too much existing view code to convert over so they will have to stick with the GWT 2 stream and hope that it remains well supported. This is the situation my company face with one of our products. So GWT 3 is not ideal for new projects and doesn't help with existing projects. Where is it's market? -- 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/342561ff-64da-4e7a-aec4-6e9b84846f09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
