Google Promises More Crashes With 'Chrome Canary Build'
Google has long maintained three distribution channels for its Chrome Web browser: A stable channel, a beta channel, and a developer channel, representing points on the continuum of code stability. Convinced that its developer channel isn't sufficiently buggy, Google is introducing the Google Chrome Canary Build, for those who really want to live on the edge.
Google has long maintained three distribution channels for its Chrome Web browser: A stable channel, a beta channel, and a developer channel, representing points on the continuum of code stability. Convinced that its developer channel isn't sufficiently buggy, Google is introducing the Google Chrome Canary Build, for those who really want to live on the edge.Google describes its developer channel thus: "This developer preview channel is where ideas get tested (and sometimes fail). The Dev channel can be very unstable at times, and new features usually require some manual configuration to be enabled. Still, simply using Dev channel releases is an easy (practically zero-effort) way for anyone to help improve Google Chrome."
Forget "very unstable at times" and get ready to move to even greater instability, with updates that arrive at a greater frequency than the weekly developer channel releases.
"We plan to update the Canary Build more frequently than the Dev channel, with riskier changes, and usually without a human being ever verifying that it works, so the Canary Build is only for users who want to help test Google Chrome and are comfortable using a highly unstable browser that will often break entirely," wrote Google Chrome product manager Henry Bridge in a blog post.
Google Chrome Canary Build is only available for Windows at the moment and it cannot be set as your default browser -- you may be able to crash more frequently but don't count on doing so conveniently.
Google is adding the Chrome Canary Build to get feedback from testers more quickly, without alienating early adopters and developers, who evidently see the developer channel as a usable future version of Chrome rather than as unfinished alpha code.
The question is where does this end? Like razor maker Gillette, which increased its blade count from one to five between 1971 and 2006, Google appears to be determined to push the envelope to the point of absurdity.
How long will it be before we see Chrome Typo Build, unfinished code that just hangs?
This fall, the leaders of the public and private sectors will convene at Gov 2.0 Summit in Washington, D.C., to discuss government's critical challenges. Request an invitation to join this unparalleled group of influencers. It happens Sept. 7-8. Click here to find out more.
Building A Mobile Business MindsetAmong 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps – and it's past time for those with no plans to get cracking.