Google (who proposed that change of direction) has only internal *customers*; we outside Google are not customers, we're a community of users of a FLOSS project. Sencha and Vaadin, and to some extent Arcbees and RedHat, *do* have customers though, and they don't seem to disagree with those changes. I suppose they'll maybe port widgets to GWT 3.0, or maybe just continue support GWT 2.8 and start fresh for GWT 3.0. Also, as Daniel Kurka said, Google does care about a migration path to GWT 3.0, as they have many internal apps to migrate. It's true however that they have the resources and tools (Refaster) to move their users to new APIs rather than make the old ones work with GWT 3.0 (e.g. RPC and widgets, as used by Google Groups among others)
-- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
