3,618 karma · joined June 24, 2009
Say what you want about Wal-Mart (I avoid them like the plague just because I find the shopping experience actively repugnant), but to go from inception to world-dominating monster in ~40 years is impressive.
I'm not sure that's what is going on in Scribd's case, though.
Compile time definitely gets better if you reduce the number of targets, but it still totally dominates most people's build times.
Not needing to recompile in dev mode is definitely a big win.
* Things like progressive enhancement and semantic markup might not be totally impossible, but they're definitely not the focus of the framework.
* The back button is broken by default; there's a work-around but you're probably used to getting that functionality for free.
* The GWT compile cycle is LONG.
* You pretty much NEED to be using Eclipse (or possibly IntelliJ) instead of your text editor of choice.
* The final product probably won't feel like most web applications.
To be fair, people have written things like [quake2-gwt](http://code.google.com/p/quake2-gwt-port/), so you can get something pretty awesome in exchange for these tradeoffs. Also, if you loathe HTML and JavaScript, but you still need to get something up on the web, then GWT might be just your ticket.
1. They feel duped. They gave some money to a person because they thought that person was down on his/her luck, then find out that they were played. People don't like being defrauded.
2. They are intellectually outraged because the beggar has made a career out of taking money in exchange for nothing of value, although some might argue that the warm fuzzies provided by the act of giving count as something of value.
3. They are angry that these beggars are destroying good will toward other beggars who are begging because they really do need help.
Of the ones I discussed, I image #1 is the biggest factor.