GMaps v3的状态 [英] The state of GMaps v3

问题描述

我即将开始一个基于Google地图的项目，并且想知道GMaps v3的发布版本是否具有v2中提供的大部分功能，或者现在是否最好坚持使用v2。
是否有任何地方有v2中尚未内置到v3中的功能列表 - 以及不在v2中的v3功能。

解决方案

就个人而言，除非您从v3功能获得显着优势，否则我会避免将v3用于实况网站，直到它从Google实验室发布出来。

< Code Labs中的API可能会随着它们的发展随时更改。他们也没有致力于3年的弃用政策，并且Google在测试和修复bug方面的责任更轻。

这不仅仅是理论上的。 get_和set_语法的更改只能同时运行几周。因为v2是一个成熟的产品，所以可以避免破坏大量现有页面的语法更改。如果你确实要用v3，那么你必须留意将来换页语法改变的可能性。

V3版本最终不得不比v2，这可能部分归因于轻量级测试，但也因为没有相当于v2.x版本。 v3代码直接从Google内部测试直接进入在所有v3网站上运行。

I'm about to start a Google map based project and am wondering if the release version of GMaps v3 has most of the features that are available in v2, or if it would be best to stick with v2 for now. Is there anywhere that has a list of features in v2 that are not built into v3 yet - and features of v3 that are not in v2.

解决方案

Personally, I'd avoid using v3 for live sites until it comes out of Google Labs unless you gain a significant advantage from the v3 features.

APIs in Code Labs may change at any time as they evolve. They are also not committed to the 3 year deprecation policy, and Google's obligations with regards to testing and bug fixing are more lightweight.

That's not just theoretical. The change of the get_ and set_ syntax only ran in parallel for a few weeks. Because v2 is a mature product, syntax changes that break large numbers of existing pages are avoided. If you do go with v3 you have to remain attentive to the possibility of future page-breaking syntax changes.

V3 releases end up having to be pulled back significantly more often than v2, that could be partly due to lightweight testing, but also because there's no equivalent of a v2.x release. v3 code goes directly from "Google internal testing" to "live on all v3 sites" in one step.

这篇关于GMaps v3的状态的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！