monkeybusiness
How Newcomers Can Influence Established Groups
Low-Calorie Diet May Extend Life in Primates
New York Attorney General Sues Tagged.com for deceptively mining email contacts
First Came Gizmodo, Then Engadget. Now, GDGT.
China Limits Use of ‘Virtual’ Currency Used In Online Gaming
Author Alice Hoffman Apologizes for Twitter Outburst About a Bad Review
For Tech Companies, Downturn Serves as Cause for Common Ground
Viewers Of Online Video Are Spending More Time On Each Clip
Thoughts on Haml
You're hired - next year
Fighting Real Parrots With a Fake Owl
You say: "GWT seems like a platform for Swing programmers who don't want to deal with JavaScript's idiosyncrasies and browser quirks." But couldn't you say the same about jQuery?
In fact, GWT requires you to understand the DOM and to get into the more advanced tricks with GWT there are features to let you write js directly in your Java code.
Not sure what you mean by "ease data transfer": "If you're doing a lot of data manipulation and storage with AJAX, GWT may actually be the way to go". Do you mean if your ajax passes a lot of data back and forth, then GWT might help because its minified and optimized?
http://www.infoworld.com/d/developer-world/flapjax-griddle-w...
Ask HN: Anyone using GWT in an app?
I was thinking about using GWT on App Engine but the more I think about it, the less I see the need for writing Java code for my client-side JS. Anyone else feel this is overkill and a JS library like jquery makes more sense?Come to think of it, is there ever a good justification for using GWT?