I've been trying to understand the reasons GWT has not become a widespread JS alternative. It has lost a great deal of mindshare; it's pretty much a niche market now. Dart appears to be Google's second crack at the whip (possibly learning from GWT's mistakes?).
There is very little discussion on the web about these reasons. Is it really because of Java's reputation for being complicated and difficult? Or could the elephant in the room be issues surrounding compiling to JS? If so, this would be the same obstacle Dart faces. So, why *did* GWT not take the world by storm? On Wednesday, 22 August 2012 18:10:38 UTC-4, Joseph Lust wrote: > > Frankly the only issue GWT has, which Dart likely does not, is that it > requires intelligent Java developers. You know, that language that is all > strict and requires you to really understand what you're doing. Generics, > oh my! > > Script kiddies don't much care for XML, unit testing frameworks, Aria, > UiBinder, i18n, hyper optmized JS and the like. To them these are hoops. I > would not expect frameworks that really are best in class at making RIA's > to be the 'most popular' for this reason. And it's not just the kiddies. To > others like seasoned JSP developers, many of the concepts are still new in > GWT, and why would they want to change? > > So I'd never expect GWT to become super popular or to surpass PHP/jQuery > mashups. But I can say from experience that in the enterprise space, where > these features are sought afters, it is continuing to gain popularity. > We've got 70 GWT devs in my office alone. > > > > Sincerely, > Joseph > -- 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. For more options, visit https://groups.google.com/d/optout.
