What are the difference between Chrome, Canary and Chromium?
- Your interpretation is correct
-
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.
Marvin Glenn Lacuna
Marvin has more than five years of diverse experience as an information technology professional in the fields of system analysis, design and development, system administration, infrastructure, database and training. He is a former Software App Architect at ABS-CBN Broadcasting Corporation under the Digital Media Division, a client-facing company that focuses on creating innovative technologies. He developed over 22+ applications during his three-year tenure that includes website and windows application development. Currently, he is working as a Senior Application Architect/Consultant in Wizardsgroup Inc. and Accenture.com where he is repeatedly being recognized for his exceptional work in developing innovative solutions on time and on budget. He is responsible in ensuring the quality of works delivered are in accordance to its best practices and provides clearer direction to the team. He has a good understanding of the over-all software lifecycle development, as a matter of fact, he puts most of his career experience on the entire lifecycle, from requirement gathering to architecture, design, coding, testing, deployment and implementation, demonstration, training and support. In addition, he is a part of the architecture team and is the youngest member, but it does not hinder him from thinking like a scientist. He drives a lot of initiatives for content users to help them save a bunch time that will eventually lead them to save a lot from their allocated budget. Marvin is a proactive person and never relies on his previous achievements. Learning does not stop in the four corners of the room for Marvin, he continuously works very hard to advance his knowledge. He always strives for the best. He always seeks timely feedback from his peers and manager and is never discouraged by criticisms. Having a can-do attitude, he is never afraid to step-out of his comfort zone and is ready to face whatever challenges that lies ahead. Marvin is a Sitecore Professional with Sitecore certifications under his belt. Marvin is aiming to become a Sitecore MVP a couple of years from now. So watch out, remember he is only a 22 year-old kid. Can you imagine that?
Updated on October 18, 2020Comments
-
Marvin Glenn Lacuna over 3 years
Here's how I understand the google browser differences:
- Chrome - Production release (the one we're currently using, stable version)
- Canary - Test release before new production release (Version prior to Chrome release)
- Chromium - Dev release and available in Linux (maintained by Ubuntu developers, no auto-update of version - user triggered)
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?)
-
ggorlen over 2 years
