... and that's a problem, at least the way it is developed now. GWT is a more-or-less open-source project. While it is indeed open-source (you can look at the code), the process of developing it depends heavily on closed-source, blackbox projects made by Google, that nobody really knows about or aren't allowed to say about.
For example: it was said that "Google uses GWT 2.8 beta internally, so it is pretty stable". Which projects? Who are the folks involved in those projects? How deep in the usage of GWT on those projects? Nobody knows, and yet the development cycle of GWT is tied to it. So GWT is not only internal to Google since the creation of the steering group, but still it depends heavily on Google - and it is not advertised as it used to be (like on Google I/O and other presentations). And by being tied to blackbox projects from Google, and since the policy of Google for release dates is "release when it's done", we, members of the GWT community outside Google, stay with little-to-no information about how and when the things will be done. It's nice to have a company like Google using GWT (is it still using? <http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dart-we-asked.html>), but the development process and communication with the community have a long way to go. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
