This would be a "discussion" not a "question" that's why I posted here.
So the "new" maps.google.com is out for a while, from the surface, it no longer uses pre-rendered tiles and everything are drawn on the client as graphics using the vector data streamed from server, could be WebGL and/or other graphics API. Although it probably won't be widely adopted until most users getting a more powerful machine to handle the demand, it seems this is where Google is heading. After all it opens a lot of opportunities to get on same page with the mobile experience on Android and iOS. That's lead to the question of what the JS API v3 is going to do, and in turn how 3rd party developers will be impacted. Will there be a dramatic V4 coming out that is non-backward compatible like V3 to V2, or those will be somehow eased into V3? For end users, when they see a website built with Google API, they probably expect similar behavior to maps.google.com. V3 has been adding features in the last couple of years to mimic maps.google.com, which has been evolving based on V2 code base until the recent release of the "new" Google map. However, this round of change seems to quite significant. Thoughts? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-maps-js-api-v3+unsubscr...@googlegroups.com. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. Visit this group at http://groups.google.com/group/google-maps-js-api-v3. For more options, visit https://groups.google.com/d/optout.
