Speed

[edit]
The JavaScript virtual machine used by Chrome, the V8 JavaScript engine, has features such as dynamic code generation, hidden class transitions, and precise garbage collection.[19]
Several websites performed benchmark tests using the SunSpider JavaScript Benchmark tool as well as Google's own set of computationally intense benchmarks, which include ray tracing and constraint solving.[173] They unanimously reported that Chrome performed much faster than all competitors against which it had been tested, including Safari (for Windows), Firefox 3.0, Internet Explorer 7, Opera, and Internet Explorer 8.[174][175][176][177][178][179] However in more recent independent tests of JavaScript performance, Chrome has been scoring just behind Opera's Presto engine since it was updated in version 10.5.[180]
On September 3, 2008, Mozilla responded by stating that their own TraceMonkey JavaScript engine (then in beta), was faster than Chrome's V8 engine in some tests.[181][182][183] John Resig, Mozilla's JavaScript evangelist, further commented on the performance of different browsers on Google's own suite, commenting on Chrome's "decimating" of the other browsers, but he questioned whether Google's suite was representative of real programs. He stated that Firefox 3.0 performed poorly on recursion-intensive benchmarks, such as those of Google, because the Mozilla team had not implemented recursion-tracing yet.[184]
Two weeks after Chrome's launch, the WebKit team announced a new JavaScript engine, SquirrelFish Extreme,[185] citing a 36% speed improvement over Chrome's V8 engine.[186][187][188]
Chrome uses DNS prefetching to speed up website lookups,[189] as other browsers like Firefox,[190] Safari,[191] Internet Explorer (called DNS Pre-resolution),[192] and in Opera as a UserScript (not built-in).[193]
Chrome utilizes the faster SPDY protocol instead of HTTP[194][195] when communicating with servers that support it, such as Google services, Facebook, Twitter, and other websites.

Enterprise deployment

In December 2010 Google announced that to make it easier for businesses to use Chrome they would provide an official Chrome MSI package. For business use it is helpful to have full-fledged MSI packages that can be customized via transform files (.mst) - but the MSI provided with Chrome is only a very limited MSI wrapper fitted around the normal installer, and many businesses find that this arrangement does not meet their needs.[43] The normal downloaded Chrome installer puts the browser in the user's local app data directory and provides invisible background updates, but the MSI package will allow installation at the system level, providing system administrators control over the update process[44] — it was formerly possible only when Chrome was installed using Google Pack. Google also created group policy objects to fine tune the behavior of Chrome in the business environment, for example setting automatic updates interval, disable auto-updates, a home page and to workaround their basic Windows design flaws and bugs if it comes to roaming profiles support, etc.[45] Until version 24 the software is known not to be ready for enterprise deployments with roaming profiles or Terminal Server/Citrix environments.[46]

Public release

An early version of Chromium for Linux, explaining the difference between Chrome and Chromium
The browser was first publicly released for Microsoft Windows (XP and later versions) on September 2, 2008 in 43 languages, officially a beta version.[21]
On the same day, a CNET news item[22] drew attention to a passage in the Terms of Service statement for the initial beta release, which seemed to grant to Google a license to all content transferred via the Chrome browser. This passage was inherited from the general Google terms of service.[23] Google responded to this criticism immediately by stating that the language used was borrowed from other products, and removed this passage from the Terms of Service.[7]
Chrome quickly gained about 1% usage share.[20][24][25][26] After the initial surge, usage share dropped until it hit a low of 0.69% in October 2008. It then started rising again and by December 2008, Chrome again passed the 1% threshold.[27]
In early January 2009, CNET reported that Google planned to release versions of Chrome for OS X and Linux in the first half of the year.[28] The first official Chrome OS X and Linux developer previews[29] were announced on June 4, 2009 with a blog post[30] saying they were missing many features and were intended for early feedback rather than general use.
In December 2009, Google released beta versions of Chrome for OS X and Linux.[31][32] Google Chrome 5.0, announced on May 25, 2010, was the first stable release to support all three platforms.[33]
Chrome was one of the twelve browsers offered to European Economic Area users of Microsoft Windows in 2010.[34]

Development

[edit]
Chrome was assembled from 25 different code libraries from Google and third parties such as Mozilla's Netscape Portable Runtime, Network Security Services, NPAPI, Skia Graphics Engine, SQLite, and a number of other open-source projects.[35] The V8 JavaScript virtual machine was considered a sufficiently important project to be split off (as was Adobe/Mozilla's Tamarin) and handled by a separate team in Denmark coordinated by Lars Bak at Aarhus. According to Google, existing implementations were designed "for small programs, where the performance and interactivity of the system weren't that important", but web applications such as Gmail "are using the web browser to the fullest when it comes to DOM manipulations and JavaScript", and therefore would significantly benefit from a JavaScript engine that could work faster.
Non-mobile web browser statistics on Wikimedia
Chrome
  
44.06%
Internet Explorer
  
22.08%
Firefox
  
18.17%
Others
  
9.07%
Opera
  
3.38%
Safari
  
3.24%
Non-mobile web browser usage for Wikimedia visitors for March 2013.[36]
Chrome uses the Blink rendering engine to display web pages. Based on WebKit 2, Blink only uses WebKit's "WebCore" components while substituting all other components, such as its own multi-process architecture in place of WebKit's native implementation.[37]
Chrome is internally tested with unit testing, "automated user interface testing of scripted user actions", fuzz testing, as well as WebKit's layout tests (99% of which Chrome is claimed to have passed), and against commonly accessed websites inside the Google index within 20–30 minutes.[19]
Google created Gears for Chrome, which added features for web developers typically relating to the building of web applications, including offline support.[19] However, Google phased out Gears in favor of HTML5.[38]
On January 11, 2011 the Chrome product manager, Mike Jazayeri, announced that Chrome would remove H.264 video codec support for its HTML5 player, citing the desire to bring Google Chrome more in line with the currently available open codecs available in the Chromium project, which Chrome is based on.[39] Despite this, on November 6, 2012, Google released a version of Chrome on Windows which added hardware-accelerated H.264 video decoding.[40] As of January 2013, there has been no further announcement about the future of Chrome H.264 support.
On February 7, 2012, Google launched Google Chrome Beta for Android 4.0 devices.[41] On many new devices with Android 4.1 and later preinstalled, Chrome is the default browser.[42]
On April 3, 2013, Google announced that it would fork WebCore to form its own layout engine known as Blink. The aim of Blink will be to give Chrome's developers more freedom in implementing its own changes to the engine, and to allow its codebase to be trimmed of code that is unnecessary or unimplemented by Chrome.[37]
Enterprise deployment[edit]
In December 2010 Google announced that to make it easier for businesses to use Chrome they would provide an official Chrome MSI package. For business use it is helpful to have full-fledged MSI packages that can be customized via transform files (.mst) - but the MSI provided with Chrome is only a very limited MSI wrapper fitted around the normal installer, and many businesses find that this arrangement does not meet their needs.[43] The normal downloaded Chrome installer puts the browser in the user's local app data directory and provides invisible background updates, but the MSI package will allow installation at the system level, providing system administrators control over the update process[44] — it was formerly possible only when Chrome was installed using Google Pack. Google also created group policy objects to fine tune the behavior of Chrome in the business environment, for example setting automatic updates interval, disable auto-updates, a home page and to workaround their basic Windows design flaws and bugs if it comes to roaming profiles support, etc.[45] Until version 24 the software is known not to be ready for enterprise deployments with roaming profiles or Terminal Server/Citrix environments.[46]

Google Chrome

Google Chrome is a freeware web browser[7] developed by Google that uses the WebKit layout engine as of its latest stable release.[note 2] It was released as a beta version for Microsoft Windows on September 2, 2008, and as a stable public release on December 11, 2008. As of April 2013, according to StatCounter, Google Chrome has a 39% worldwideusage share of web browsers making it the most widely used web browser in the world.[11] Net Applications, however, indicates that Chrome is only third when it comes to the size of its user base, behind Internet Explorer and Firefox.[12]

In September 2008, Google released the majority of Chrome's source code as an open source project calledChromium,[13][14] on which Chrome releases are still based.