Does Google have any statements or guiding principals about the support of existing API's as new releases are rolled out? What has been the experience to this point?
Are there "best practices" a GWT developer can do to insulate the apps from API changes through releases? If so, are they covered in the book?
Why I ask this question: At our local Java user group meeting the other night, one of the programmers was complaining about a framework not supporting applications in future releases; how a certain framework rquired a re-write of the apps for the newest release of the framework. I think he was complaining about Tapestry, but I'm not sure.
Back support for older API's is always an issue with languages, operating systems, and frameworks.
Originally posted by Charles McGuire: Are there "best practices" a GWT developer can do to insulate the apps from API changes through releases? If so, are they covered in the book?
Stay away from, or at least be highly aware of experimental aspects is really the best advice.
GWT contributors also make the best attempts to protect you too - most of GWT is stable but in the latest release there are a couple of widgets where the internals are not completely sorted out. Methods affected in this case they have been marked final to prevent eager people subclassing minimising the chance of being caught out if changes occur in future release.