GWT is still alive and well. 2.5.1 is getting released soon, and work is happening on 2.6 already.
The main reason why there is less attention being paid to GWT is that it is a mature library; there's still lots of work and maintenance to do, but as for the core features, it's all there already. The main purpose for choosing GWT is a) the compiler's optimization power and b) java tooling. If another part of your project, for example, the server, is written in java, choosing GWT is a no-brainer. Either you can share some code, or rewrite it all in javascript, then keep them synced. Also, if you use maven in your project, integrating gwt into your build allows you to drop in libraries and frameworks no sweat. If you have use for java in your project, choosing GWT is very viable. If you just need a client side framework to bang out a quick project, you can use jquery (or, if you still want the compiler's prowess, look at GQuery, which is a jquery clone in java). GWT has a higher initial investment than a plain javascript framework, but it pays dividends in the end; if you plan to have a long lived or large project, choosing GWT just for the type safety and ability to refactor alone make it worth your while (without regard to all the other goodies). -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
