I agree 100% with your assessment of alternative technologies, and agree that GWT is really the only solution for developing complex web applications. The only alternative is a 100% Javascript solution (for example using Closure tools). With Dart, Google have acknowledged that Javascript isn't really up to the task. Given Google's reliance on GWT for some of their core applications, I think it's fair to assume either GWT will be around for a while or there will be some migration path to Dart.
On Apr 14, 12:34 am, Blake McBride <blake1...@gmail.com> wrote: > > Now we have ASP, JSP, and other popular mashups out there. I am utterly > shocked how poor they are (although to their credit, they are trying to > solve practical problems given an environment that was clearly not meant to > support what they are attempting!). These environments are among the worst > I've ever seen. It's one kludgy work around after another with three > totally different environments attempting to interact. GWT goes a very > long way to solve this very significant problem. However, GWT is a total > waste of time if you risk your entire company on it and it gets dropped. > In terms of financial risk, very unfortunately, tool popularity and > support beats functionality, elegance, and productivity every time. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
