Google Chrome – Placing blame where it belongs
It seems like everyone’s talking about the Google’s latest hit to the market. A brand new browser, built from scratch as claimed by Google. Google has launched the secret project days after the rival Microsoft released its revolutionary IE8’s beta 2 release. Features are pretty much the same for both the products; we’ll see what Chrome is actually supposed to offer:
Stable
Browser crashes are new to none. Google always seem to have realized the value of saving an email draft from getting vanished due to browser crash by enabling auto save in its Gmail application.
Faster
Google Chrome is always ready to listen to a click. Click it and it open in a blink which proves its minimal memory consumption and fast performance.
Secure
With its built-from-scratch release, Chrome already ensured security being new-to-world technology. There are warnings at every step to make sure that users enter the secure place at their own risks.
Clean
No extras! Google Chrome is clean and has all the space available for web pages. There’s no title bar, no status bar and no toolbars, just one tabs bar that also works as title bar and all of remaining space belongs to the page you’re opening.
Simple
With simplicity transferred straight from Google’s homepage Chrome delivers Google’s trademark simplicity and usability.
Efficient
Whether it’s opening or closing the tabs or opening heavy web applications, Google Chrome is efficient and puts everything in front right when ordered.
Open Source
Being an open source application, Chrome invites and accepts contribution from global community. So your feedback and contribution is welcome.
Multi-threading
Ever heard of a browser that based on multi-threading? Chrome is the one! With its threaded approach it resolves the issue of browser crashes by keeping heavy applications allocated in a separate thread so that it doesn’t affect overall browser functionality and performance.
Multi-processing
Every window and every tab of Chrome opens as a new process. If you see in task manager, every instance of Chrome, whether a tab or window has a separate process, with different processing and memory allocated to it, and if one process stops responding, it doesn’t affect other processes unlike in legacy browsers.




Add a comment