以下是我对Google浏览器差异的理解:
$ b是否还有其他要点我错过了?就开发而言,如果我使用Chromium和Canary而不是Chrome,是否还有其他考虑? (缓存?)
解析方法 您的解释是:缓存,兼容性,cookie,性能等正确的 Canary基本上是一个由Chrome回购的树状结构构建的夜间版本。这是开发的前沿,因此您应该期望崩溃和错误,但它是测试最近对Chrome进行更改的最快捷方式。 (除了自己建设ToT外) 除了Canary,还有一个Dev频道,这个频道的发布时间稍长一些,通常每周大约一次,但仍然是从流血的边缘尖的树。 Beta频道是即将发布的长时间运行的分支,通常非常稳定/无bug。 b $ b 从新鲜到稳定的顺序:金丝雀 - >开发 - > Beta - >稳定
不同版本之间面向网络的API的兼容性应当基本相同,当然,即将进行的即将进行的更改除外。一般来说,Canary,Dev,尤其是Beta中发生的变化旨在使其成为稳定频道,因此在测试您的应用程序与Beta时测试您的应用程序是一个不错的主意,以确保您的应用程序在升级Beta后将继续按预期运行稳定。您可以在 ChromeStatus 上找到即将对Web API进行的更改。
在Canary和Dev,你很可能会遇到在开发过程中无意中发现的错误。如果您想帮助Chrome开发人员,可以在 Chromium bug跟踪器上为这些问题提供错误(使用此方法查找Stable / Beta渠道中发现的错误)
在性能方面,手工制作的Chromium将取决于是谁制作的以及使用哪些标志。加纳利/ Dev / Beta / Stable之间的表现应该具有可比性,并且表明最终的稳定版本。
Here's how I understand the google browser differences:
Are there any other points that I missed? And in terms of development, is there any other consideration if I use Chromium and Canary rather than Chrome? Like caching, compatibility, cookie, performance and etc. (bugs?)
解决方案Canary is basically a (near) nightly release built from the current tip of tree of the Chrome repo. It's the bleeding edge of development and so you should expect crashes and bugs but it's the quickest way to test recent changes to chrome. (Aside from building ToT yourself)
Aside from Canary, there's also the Dev channel which is a slightly longer development release, usually about weekly, but still built from the bleeding edge tip-of-tree. Beta channel is a long running branch that's the upcoming release and is generally quite stable/bug free.
The order from "freshness" to "stable": Canary -> Dev -> Beta -> Stable
Chromium is the name of the open-source project from which Chrome is built. A Chromium build is basically equivalent to Chrome but doesn't include proprietary bits (Flash plugin, codecs, etc) or official Google branding (icons, etc).
Compatibility in terms of web-facing APIs between the different versions should be essentially the same except, of course, for intended upcoming changes. In general, changes that occur in Canary, Dev, and especially Beta, are intended to make it to Stable channel so it's a good idea to test your apps against Beta to make sure your app will continue to function as expected once the Beta is promoted to Stable. You can find upcoming changes to Web APIs at ChromeStatus
In Canary and Dev, you're more likely to run into unintentional bugs that creep in during development. If you'd like to help Chrome development you can file bugs for these at the Chromium bug tracker (use this for bugs you find in Stable/Beta channel too!)
In terms of performance, a hand-built Chromium will depend on who built it and with what flags. The performance between Canary/Dev/Beta/Stable should be comparable and indicative of the final stable release.
更多推荐
Chrome,Canary和Chromium有什么区别?
发布评论