Google keeps pushing ahead, drops first version of Chromium 6

Here come the shouts of version jumping, ladies and gentlemen: Google has pushed the Chromium browser to version 6. If you're keeping tabs, the first publicly available version of Google Chrome arrived on September 1, 2008. About a year and a half later, they're 5 versions deep.
It's not as if Google just randomly decides when they want to bump the version number. Google has clearly documented reasons for why they make the change. Typically it's when major changes to either WebKit or the V8 JavaScript engine are made. (edit: Chromium v6 appears to have bumped WebKit to v 58855, which was released about 5 days ago). Still, I wonder if Chrome will hit version 9 before Internet Explorer does.
And hey, it's just a number -- right? To you and me, yes.
To the general computing public, though, bigger still means better -- and the average Joe just might be more receptive to a Chrome browser with a 6 after it than Firefox with a 3.
6 is twice is good as 3, right?
Builds stamped V6 are only available on the Chromium buildbot server right now -- but you'll be seeing the change in the Dev Channel as soon as update scheduled for tomorrow. We'll have a look at the changelog once it's posted.
It's not as if Google just randomly decides when they want to bump the version number. Google has clearly documented reasons for why they make the change. Typically it's when major changes to either WebKit or the V8 JavaScript engine are made. (edit: Chromium v6 appears to have bumped WebKit to v 58855, which was released about 5 days ago). Still, I wonder if Chrome will hit version 9 before Internet Explorer does.
And hey, it's just a number -- right? To you and me, yes.
To the general computing public, though, bigger still means better -- and the average Joe just might be more receptive to a Chrome browser with a 6 after it than Firefox with a 3.
6 is twice is good as 3, right?
Builds stamped V6 are only available on the Chromium buildbot server right now -- but you'll be seeing the change in the Dev Channel as soon as update scheduled for tomorrow. We'll have a look at the changelog once it's posted.













Comments
5
Subscribe to commentsbox750May 10th 2010 12:55PM
Opera is now at number 10 and it has taken them years to get there, still one of the best browsers, Chrome should take it easy with the numbering thing.
SonnyjimbaMay 10th 2010 1:03PM
This is another thing I love about Chrome- constant updates, if they say they're adding something (e.g theme syncing) you can be sure to have it in the dev/beta channels in very little time, because they don't wait to release it in a massive update, as opposed to FF, Opera etc ,which other than security, have fairly slow update schedules.
I'm not saying they're bad browsers ;) they are great, but I prefer the way Chrome is updated rather than the big bundled updates of FF etc.
Just my opinion though =)
laeroMay 10th 2010 3:03PM
Second that, even better would be rolling releases. But then there would be no version number, which I guess the general public would find strange.
Hugh Isaacs IIMay 10th 2010 2:07PM
All this update brings is a few tweaks to the coming App Launcher feature.
AndrewWhiplashMay 10th 2010 10:09PM
The only thing about Chrome is that it doesn't display the version number anywhere.
The version number doesn't appear anywhere on the download site, or in the "main functions" of the browser. The version number only appears when a user going to wrench>"about Google Chrome".
Along with the auto update feature of Chrome, the version number is irrelevant to 98% of end users.