I'm a bit surprised that there hasn't been more comment on the direction the GWT team plan to take GWT in 3.0.
I've been involved in a GWT project over the last 18 months or so where we're developing a large line-of-business app which we expect to have a lifetime of potentially a decade or more. Most of the GWT tech we've used (UIBinder, GWT-RPC, gwt-user stuff, CssResource, etc - basically all the "best practices" advice from the last few years) is going, so by the time we're ready to deploy, and GWT 3.0 comes along, our app is obsolete.
Right now I'm not too sure if the there's any value in continuing with GWT. The value proposition (using Java front to back) seems to be going away.
Where does the new web asm stuff just announced by all the browser vendors fit in ? Javascript will no longer need to be the transpile target.
-- I've been involved in a GWT project over the last 18 months or so where we're developing a large line-of-business app which we expect to have a lifetime of potentially a decade or more. Most of the GWT tech we've used (UIBinder, GWT-RPC, gwt-user stuff, CssResource, etc - basically all the "best practices" advice from the last few years) is going, so by the time we're ready to deploy, and GWT 3.0 comes along, our app is obsolete.
Right now I'm not too sure if the there's any value in continuing with GWT. The value proposition (using Java front to back) seems to be going away.
Where does the new web asm stuff just announced by all the browser vendors fit in ? Javascript will no longer need to be the transpile target.
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+unsubscribe@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.
No comments:
Post a Comment