gwt's pretty amazing, but I think it takes a good six months to really understand it all. If the implementors of those sites hate typing and hate java, they'll never get to the point where they appreciate gwt.
Seems to be there's a strong anti-Java sentiment these days. Big, static typed languages aren't that cool now, and people are able to make nice apps in dynamic languages (Ruby, Javascript). Churning java into javascript is kind of weird (or at least novel) and it takes a while to really get it. jQuery is tight -- you can do a lot in one line of code. That sort of stuff wins developers over. To me, gwt realy comes down to turning java into really tight cross- browser javascript with clean abstractions for ajax'y apps. If that's not a sale for you (ie, you hate java), then jQuery is probably the next stop in the evaluation path. On Nov 22, 9:58 pm, adam <[EMAIL PROTECTED]> wrote: > I see herehttp://docs.jquery.com/Sites_Using_jQuerythat lots of big > projects, most of which are probably led by some smart, deep-thinking, > open-minded individuals, are using jQuery and hand-written javascript. > I notice that this list of projects using > GWThttp://www.ociweb.com/mark/programming/GWT.html#WhoIsUsingItdoesn't > look as impressive. > > Why are leaders on big projects deciding to use tools other than GWT? > Do they have any good reasons to not use GWT? Should they use GWT? If > so, why? > > If this has already been covered in another post, please point me to > it; no need to reinvent the wheel. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
