Hi Herb, There is no reason to rewrite existing v2 applications, nor is any existing investment in v2 wasted. The deprecation of v2 is simply our way of being open and honest with developers such as yourself about our plans for v2. It serves as notice that there will be no new features. However we are by no means pulling the rug out from under v2. It would suicidal for us to do so given the level of adoption it has, notwithstanding the fact that it would be a clear breach of our own deprecation policy.
v2 will continue to be maintained and supported. We will continue to fix bugs in v2, and support the same set of browsers. If anything v2 will become more mature and stable than at any time in it's history as the remaining bugs get addressed and no new features arrive to destabilise it. The deprecation policy commits us to maintaining v2 for at least 3 years, and that's just the minimum rather than a hard stop. We understand that the word 'deprecation' has negative connotations, but it's really just the warning you are looking for, with a 3 year notice period. It's not a hard switchover, just a change of relative priority. We could have chosen not to deprecate v2, but given that there are no new features on the v2 roadmap we felt that it would have been disingenuous not to do so. Hope that helps to clarify and assuage any fears, Thor. On May 25, 4:43 am, SpoilsportMotors <[email protected]> wrote: > On May 24, 8:29 am, "Thor (Google Employee)" <[email protected]> > wrote: > > > I can assure you that there was nothing hasty about this decision. We > > have been planning it, and working towards it, for some time. > > Perhaps not hasty, but it's been a surprise - and not a good one - > that it came now. It may well be that it was announced that the > switchover would occur around this date some time ago, but I've missed > it. I suspect that others in the same position I am - developing > products and services based on the Javascript API feel a little shell- > shocked with the announcement, and the (again, apparent) lack of > warning or timeline. I've started a project to be completed in a > couple of weeks that could use the v3 API, and probably would have had > we know it was going to be official by the time we hit our go-live > date. Now it feels rather like we've invested several man-months of > effort on something that's going to have be largely rewritten, and > it's not a good feeling at all. > > Thanks for letting me vent my spleen a bit. > > Herb. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps API" 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 > athttp://groups.google.com/group/google-maps-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-maps-api?hl=en.
