Google would not drop support until they had something better to replace it, and a migration plan for the GWT developers. From a rational point of view, they would choose this path and keep developers' mindshare rather than loose it to some other platform/company.
They might not be making money off of people using GWT, but it keeps developers from potentially turning against them. e.g. you switched to a technology that will never work with gears, or some other Google product. On Fri, Aug 20, 2010 at 4:59 PM, Falcon <[email protected]> wrote: > I would imagine that Google will continue to improve GWT so that they > can build future applications themselves. I would think the big two > they would use internally would be Closure and GWT, so as long as > Google is making web-based apps, I doubt you have much to worry about, > as they need the tools as well. > > On Aug 20, 11:11 am, David Pinn <[email protected]> wrote: >> Perhaps it's the demise of Wave; or maybe I've just been hanging out >> with too many Ruby fan boys; but I'm nervous about the future of GWT. >> >> I have a huge investment in GWT, in terms of learning and effort, not >> to mention a sizeable and growing code base. >> >> Please tell me that GWT isn't going away. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > 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. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. 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.
