Google Chrome is an open source web browser developed by Google. It builds on parts from other open source software, including WebKit and Mozilla. The name comes from the graphical user interface frame, or “chrome”, of web browsers. The open source project behind Google Chrome is known as Chromium.

A beta version for Microsoft Windows was released on 2 September 2008 in 43 languages. Mac OS X and Linux versions are under development and are going to be released after the Windows version. Now the recent version of Google Chrome Browser is released as Chrome 2.0. If you are an existing user you can upgrade through the menus available on Chrome, if it has not automatically detected and upgraded.

[More Information & Features:]

New Features of Chrome 2.0:-

Improved New Tab Page:
The most requested feature from users was the ability to remove thumbnails from the New Tab page. Now you can finally hide that embarrassing gossip blog from the Most Visited section.

Full Screen Mode:
If you’ve ever given a presentation or watched a large video using Google Chrome, you might have wished you could use every last pixel on your screen for the content. Now you can hide the title bar and the rest of the browser window by hitting F11 or selecting the option in the Tools menu.

Form Autofill:
Filling out your information in forms over and over again can be tedious. Form autofill helps by showing information you’ve previously entered into the same form fields automatically. If at any point you want to clear out your information, that’s easy to do from the Tools menu.

Increased Stability:
Google Chrome is more stable than ever — we have fixed over 300 bugs that caused crashes since launch.

Increased Speed:
Making the web faster continues to be our main area of focus. Thanks to a new version of WebKit and an update to our javascript engine, V8, interactive web pages will run even faster. We’ve also made sure that javascript keeps running fast even when you have lots of tabs open. Try opening a bunch of web applications and then running your favorite benchmark. You can read more about V8 in our javascript scalability post on the Chromium blog.

Google has released the beta version of a new browser, Chrome. In its comic-book preannouncement, Google stated correctly that watching videos, chatting, and even playing Web-based games didn’t exist when browsers were first invented. Google wants the browser to help users focus on the applications and pages they are viewing, rather than on browser toolbars and buttons. Google has rethought the Internet browser–some of its basic underpinnings are quite novel–but users will recognize some features as they exist in other, open-source browsers on the market today.

At the moment, only the Windows version of Chrome is available for download. Plans call for Mac OS X and Linux versions in the near future. That said, Google has released Chrome in 43 languages and in 122 countries.

Chrome is based on the open-source project Webkit, the same rendering engine used by Apple Safari. If a page renders in Safari, it will render in Chrome. Webkit is also the basis for Android, Google’s mobile platform, so it seems that Google is planning to use Chrome in mobile environments.

The interface in Chrome is very different from other browsers and takes a little getting used to. Instead of the traditional Netscape/IE-style toolbar across the top, Chrome puts tabs across the top. Moreover, the tabs are detachable, so the terms “tabs” and “windows” become interchangeable within Chrome. Detached tabs can be dragged and dropped into the browser, and tabs can be rearranged at any time.

New tab pages display your nine most visited Web pages, as well as the searches you perform most, and your most recent bookmarks. Within each tab are individual controls, such as forward and back buttons. Missing is the search box. Instead, Chrome sports a hybrid address bar, which Google calls the Omnibox. The Omnibox includes not only suggestions for URLs culled from your browser’s history, but it also includes search suggestions from Google. URL Auto completion in Chrome is for top-level domains, not just some individual page you last visited on a site. There are also other neat additional elements; for example, if you go to Amazon and type within its search box to find a book or CD, Chrome remembers that Amazon search and when it next suggests the Amazon URL in the Omnibox, it also include a link to Amazon’s search box.

Application Shortcuts is a feature that allows you to create desktop icons for Web-only applications, such as Gmail or Calendar.

And there’s a stealth mode, as well. Like IE8 InPrivate, Chrome has its own incognito mode. The Incognito window looks different: it’s darker and has a little detective character in the upper left corner to help you remember it’s not remembering the Web sites you visit. Although the Omnibox in Incognito has access to the regular Chrome history, everything typed into that stealth tab will be erased when you exit, as though you were never there.

Chrome deals with pop-up dialogues in a novel way. Pop-ups associated with a Web page appear within that page’s tab, so if you want to see a pop-up in greater detail, just drag it out into its own new window. This carries over to downloads as well. Instead of using a pop-up dialogue, downloads are shunted to the bottom of the tab frame where you can monitor or interact with them if you wish.

Because of isolating each tab’s process, if one tab in Chrome crashes, the entire browser does not. This is similar to a feature within IE8 beta 2. In terms of security, isolating tabs means each tab is in its own sandbox. Applets launched on a page within Chrome are read-only, do not install to the operating system, and cannot access data already on the hard drive.

For performance, Google emphasizes speed. According to Google says, most browsers are singled-threaded, so that when a browser starts a Javascript process, it waits until that process ends. Sometimes the process gets stuck and the browser freezes. What Google has done is to create a multithreaded browser, one that can process several Javascripts at once, for example. In Chrome, one tab can be busy doing one thing while you’re off on another tab doing something else. In our CNET tests, we did occasionally see the “Aw, snap” page used when Chrome just can’t render a site.

To diagnose why a page didn’t load, there’s a task manager within Chrome, allowing you to see what process is using memory, even within the plug-ins running on that tab. So, if a Shockwave or Flash file is consuming a lot of memory and preventing a page to launch, you can shut down that process and still load the page.

Google acknowledges up front that having separate processes for separate tabs will create more memory usage, but the Mountain View company says the browser will use less memory over time. For example, when you close a tab in Chrome, you end the memory process completely, freeing up more memory for future use. In a traditional browser, fragments remain running in case you want to reopen the closed tab or as an artifact in how new tabs are created in old browsers. Chrome features enhanced garbage collection, migrating or generally sweeping up pointers as needed instead of leaving them behind. The trade-off, of course, is that closed tab pages cannot be reopened, a feature currently available in Firefox 3 and IE8 Beta 2.

Chrome includes its own Javascript Virtual Machine called V8. Google says that existing JVMs were designed to run tiny applets on Web pages, not full applications of the kind that Google makes today. Among the changes within V8, Chrome combines similar Javascript classes for better optimization, and it doesn’t interpret Javascript but converts it to machine code to execute on the CPU, which speeds up the process. V8 is also open source and will be available to developers wanting to use it in the future.

How stable is this beta from Google? Google caches hundreds of millions of Web pages for its search engine; the Gears folks say they’ve been able to test Chrome on millions of pages within seconds of completing each new build. Using Google page rank, they test against the most popular sites. With public beta testing, they’ll start testing against some of the more niche pages on the Web.