To add to David's answer: we use GWT extensively internally and externally as well. There are a number of products that launch quickly using GWT/App Engine. One of the ads tools administrative interfaces also runs on GWT. While Wave was definitely the highest profile GWT application, just keep your eyes open anytime you are using a Google tool. You'd be surprised how dependent we are on it for rapid iteration.
On Thu, Aug 26, 2010 at 10:54 AM, David Chandler <[email protected]>wrote: > David, > > Thank for your honest feedback and your enthusiasm for GWT. Google > uses GWT in many other apps besides Wave and continues to increase > investment in GWT as part of Google's overall interest in improving > user experience on the Web. In addition, it is an open source project > with a very active community of open source frameworks built on GWT. > The GWT community and code base continue to grow very rapidly, which > has made it challenging to respond to bug reports (many of which are > actually enhancement requests), much less this forum. Being new to the > GWT team (==continuing Google investment in GWT), it is one of my > personal objectives to give the community a better sense of the > exciting ways in which the GWT team continues to improve GWT. > > At this time, there is a lot of activity around the 2.1 release, and > you can get some sense of this by watching the SVN trunk. In addition, > the GWT team has considerably stepped up maven support (see recent > blog posts), which was one of the top issues in the issue tracker. As > always, addressing particular bugs is a question of priorities, but > rest assured that the GWT team is well aware that no one wants to see > new features added at the expense of stability. > > As for the @CssResource issue, if this is still unresolved for you, > please star issue 4903 (http://code.google.com/p/google-web-toolkit/ > issues/detail?id=4903) and we'll revisit it. > > /dmc > David Chandler > Google Web Toolkit Team > > On Aug 26, 4:40 am, stuckagain <[email protected]> wrote: > > Hi, > > > > Since I get no response from the GWT dev-team on reported bugs I am > > beginning to wonder about the future of GWT. It looks like stability > > of the existing features is not very high on the list. I've heard > > excuses in all the previous release that you guys were going to sort > > out long-standing bugs after the next major release ... but years have > > passed now and the collection of open and even new issues is going in > > the wrong direction. > > > > So I have to ask the obvious question: > > Is Google going to abandon it now that Google Wave has been axed ? > > > > The focus of 2.1 seems to be fast app development for enterprise apps, > > which is very good... but one of the major requirements in enterprises > > when selecting a toolkit is the maturity and stablity of the toolkits, > > how much support do you get, how fast are bugs fixed ... etc... right > > now I find it harder every day to sell GWT for newer projects. > > > > From that perspective I'm not that sure that I would want to rely on > > the Spring-Roo and Data aware widgets. > > > > When we report bugs on other opensource projects (like struts in the > > past or eclipse and many others) the new bug reports are quickly > > detected and you get some basic feedback... right now the issue > > tracker seems like you guys are using the SUN bug database. There are > > still important bugs open from the beginning years of Java! > > > > One other remark about dogfood: > > How come I can not use CssResource with the standard widgets of GWT ? > > They all rely on primary stylename and style dependent names to switch > > states ... which makes it impossible to optimize the CSS with > > CssResource. Are we really supposed to write our own widgets ? Writing > > our own widgets is not too hard, but I hate it when I can not even use > > the most fundamental UI widgets. > > > > Again: I'm sounding very negative above, but that is just because I > > care about the success of GWT! I want it to succeed but it needs to > > grow up. > > > > David > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- 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.
