When you're ready to deploy, GWT will compile your Java into optimized, cross-browser(!) Javascript. It actually creates a separate version of the code for every browser, and then loads the correct one at runtime.
GWT is still quite young, so there are still a few bugs hiding. Today we found a (minor) bug that forced us to change our JSON format. Apparently, AutoBean doesn't handle '-'(dash) characters in JSON very well, even though it's a legal JSON character. GWT will try to create a Java/Javascript variable name with a '-' in it, and this causes parsing exceptions. I'll report this at some point soon.
Even with a few rough edges, GWT seems like it really accelerates web development. You should give it a try.
Interesting piece of software will take a look.
ReplyDeleteYou should run the results through Rhino and see what you get back.
ReplyDeleteSounds like a really nice environment for web development, with some handy tools/APIs. Glad that Google doesn't hate you. ;)
ReplyDeleteAlso, GWT isn't the only thing that has trouble parsing JSON. Crazy trailing commas and all...