On July 22, Google, being all about speed, announced that they were going to shorten the release cycles of new, stable versions of Chrome from quarterly to 6 weeks. With this announcement came the Canary release channel.
In this article, I am going to explain exactly what Google Chrome Canary is and why you should be excited about its release. I will explain the meaning of its name, as well as its overall purpose in the grand scheme of things.
Why Call It Canary?
By calling the release Canary, Google is referring to the old technique of using canaries in coal mines. Back in the day, coal miners used to bring canaries down in the mines with them as a precaution. If there was any kind of deadly gas build-up, the canary would be the first to die. If the canary died, everyone knew it would be a good idea to leave the mine as soon as possible.
Chrome Canary offers the same set of precautions. The Canary build is less stable, but it will be used to test even more cutting-edge features than the developer’s build, which already tests new features before they are pushed to the beta build. If a change “kills” Chrome Canary, Google will block it from the developer build.
What’s Different About It?
Chrome Canary is somewhat of a mix between the Chrome developer build and the Chromium snapshot builds. It can be run side-by-side with any other channel, which is a new feature. This means that it isn’t linked to your other Chrome installs and can therefore run different sync profiles, themes, apps, and use different preferences.
Unlike the other channels (beta and dev), Canary’s side-by-side feature allows builds to be installed without overwriting a regular Chrome build, which means that, technically, you can install both a Canary build and a regular build that could be on the stable, beta or dev channel.
If you install Chrome Canary, you will notice that it has a different, all-yellow icon instead of the multi-colored Chrome icon or even the all-blue icon you might be accustomed to. Also, the skin of the browser is blue, helping you tell it apart from other versions of Chrome as well.
[Note]: As Canary is a secondary installation of Chrome, you cannot set it as the default browser. Also, it is currently only available on Windows.
Why Is It Necessary?
Giving users the option to run a more advanced version of Chrome without having to fully commit to alpha testing it should help increase the number of people willing to use the browser.
Canary will auto-update more frequently than any other versions available to developers. Google is working on making it update as often as they have successful nightly builds, according to their developer’s email list. When something doesn’t work on the Canary, you can just fall back on your beta version.
Also, by speeding up the Chrome development cycle, it will begin testing new features with the public and collecting feedback more quickly. The data – especially crash statistics – that they get back from users will help them find (and fix) regressions in the software faster.
[Note]: Since the Canary version of Chrome will be very unstable, it should only be used by those who are willing to risk losing browsing data in the event of a program crash.
Well there you have it. As I stated earlier, I use Google Chrome as my browser, so I am quite pleased with the news of a faster development cycle. Google seems to be very enthusiastic about getting their browser to the top and surpassing Mozilla once and for all.
From a user’s standpoint, I think this is good news for all of us. Quicker releases mean better features, and better features for Chrome should inspire some of these other companies to pick up the pace with their browsers as well.
What do you think of this news? Will you be giving Canary a try?
Leave your thoughts, ideas, and comments below, and please share this story with others if you found it useful.
Image Credit: Thepollen