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.Ĭhrome 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.
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. To that end, Google has designed an almost completely new Web browser. Clearly Google is unhappy with the current state of browser geopolitics and feels it needs to roll its own in order to ensure a robust base for its myriad hosted applications (e.g. They're back! Just when you thought the "browser wars" were over, with the two camps - Microsoft and - settling in for a kind of intransigent détente, along comes Google to stir things up all over again.
0 kommentar(er)
