Chrome beta hits v.10, Chrome dev hits v.11

Faster JavaScript, pasword sync, and video acceleration reach a wider Chrome audience. And due for version 11: "chromoting."

Chrome sped up its V8 JavaScript engine with the Crankshaft version in Chrome 10.
Chrome speeds up its V8 JavaScript engine with the Crankshaft version in Chrome 10. Google

Google released two new versions of Chrome yesterday, version 10 for beta users and version 11 for developers willing to put up with more instability.

With Google's six-week update schedule, the new releases are milestones that Chrome users pass--often not necessarily noticing given the software's silent auto-update mechanism . But there are significant new features coming with the new beta.

Top on Google's list is faster JavaScript with the "Crankshaft" version of the new V8 JavaScript engine. JavaScript runs increasingly sophisticated Web-based applications such as Google Docs, and this highly competitive aspect of browser performance has become even more so with the "Chakra" engine in the forthcoming IE9 from Microsoft.

Crankshaft leaps ahead 65 percent on Google's own V8 benchmark suite. Note, though, that faster JavaScript is only one aspect of overall browser performance, and that other benchmarks such as Mozilla's Kraken can yield different results.

Also in Chrome 10 (Windows | Mac | Linux) is hardware-accelerated video, which can increase computing efficiency and spare battery life; settings controls that move from a pop-up dialog box to a browser tab; and password synchronization among different installations of Chrome (though not, as with Firefox, with Chrome on Android).

Google isn't talking much yet about its Chrome 11 (Windows | Mac | Linux) plans, but it looks like one interesting feature on the way is "chromoting," which lets a Chrome browser remotely take over another machine over a network. It's not unlike LogMeIn or other remote desktop applications, but those can't be installed on a Chrome OS machine, so chromoting gives a browser-based mechanism. That, in turn, would let Chrome OS in effect remotely run some native software that wouldn't run on a Chrome OS machine.

About the author

Stephen Shankland has been a reporter at CNET since 1998 and covers browsers, Web development, digital photography and new technology. In the past he has been CNET's beat reporter for Google, Yahoo, Linux, open-source software, servers and supercomputers. He has a soft spot in his heart for standards groups and I/O interfaces.

 

Join the discussion

Conversation powered by Livefyre

Show Comments Hide Comments
Latest Galleries from CNET
The most anticipated games of 2015
Tech industry's high-flying 2014
Uber's tumultuous ups and downs in 2014 (pictures)
The best and worst quotes of 2014 (pictures)
A roomy range from LG (pictures)
This plain GE range has all of the essentials (pictures)