Google has designed an almost completely new Web browser. In fact, other than the core rendering engine -- which is based on the open-source WebKit standard of Safari fame -- everything in google chrome constitutes a rethinking of how you engineer a browser application. For example, with the current versions of Mozilla Firefox and Internet Explorer, individual Web page tabs are hosted in a single process -- a model that is efficient (in terms of memory and resource consumption) but also prone to catastrophic failures: A single crashed tab can easily take down the entire browser application.
Chrome seeks to eliminate this problem by isolating each tab within its own application process and then leveraging the built in memory protection capabilities of modern, preemptively multitasking operating systems to keep code and data in a failing tab from stomping on other processes. So now, when that buggy Flash applet on your favorite humor site goes belly up, it won't necessarily take down the entire browser -- the processes running in other tabs will keep chugging along.
So i love Google Chrome and See this is the best browser in current scenario.
1 comment:
Great post Ritesh. It has been told that IE 8 also will have seperate process for each tab but dunno it will catch up Chrome's speed or not. One thing still in debate that seperate process means it will take much memory. WebKit is one of the best KHTML rendering engine and it is also used by Konqueror. Also the Javascript virtual machine V8 speeds up JS a lot.
Post a Comment