This afternoon, Google has celebrated what he called the release of a much faster version of its browser Chrome. Depends on what it means by release.

Up till now, Google had distinguished development paths 1 and 2 of its web browser Chrome. Track 1 (last known version 1.0.154.65 construction) was the company ‘editing s production, however a link to the page where you can download 1.0 may cause you to test to release to the Instead, version 2.0.177.1. Google ’s have always been interesting variations on beta theme.

Anyway, today the company stated on its blog that it ’s updated at a faster version chromium, citing internal points of reference giving Javascript treating 32.1% in the best speeds new version over the old version. Well, this new version – as Betanews checked today – is really 2.0.177.1, which is the same new version it ’s held for a few weeks now. Users of version 2 – what other services were distributed as the most recent release – does not note any difference in performance.

The difference is that few users will see is that there ’s choice of any trial version more, and Google ‘ download page s door directly to the user 2.0.177.1 for the first time. Gone are the links to the 1.0 edition, and users can build with 1.0 (or can not) record their browsers are updated as we speak. In fact, in examining Betanews Thursday afternoon, download speed of Google ’s server was nothing that anyone would like shouting about rooftop.

Making the web faster continues to be our main area of focus reads a post on the blog of chromium by the engineer Darin Fisher Chrome this afternoon. With a new version of WebKit, and an update to our JavaScript engine, V8, interactive web pages will work even faster. We le ‘VE have also made sure that Javascript is continuing to work quickly even when you have a good number of labels available. Try opening a web applications and then run your favorite landmark.

As for anyone that ’s confused by the version numbers, Fisher said, we ‘ on to refer to this as chromium 2, but that ’s mainly a metric to help us maintain changes internally. We put ‘t give too much weight to the number of version and continue to run the updates as often as useful as possible.

Betanews tests (which do not Google ’s the own algorithm V8 benchmark, preferring to use the tests in place independently developed or derived) show that the final construction of the 2 Google Chrome was about 16.3% faster than the 1 pass bichromate of potash on a virtual system identically configured test. Prompted by requests for reader Betanews establish a new platform physical test that will allow us to measure the performance under different versions of Windows on the same hardware.

No related posts.