Alex Rivera | Logout

Where is the chink in Google Chrome's armor?

Asked 2008-09-04T00:26:55.300
18

While browsing with Chrome, I noticed that it responds extremely fast (in comparison with IE and Firefox on my laptop) in terms of rendering pages, including JavaScript heavy sites like gmail.

This is what googlebook on Chrome has to say

  1. tabs are hosted in process rather than thread.
  2. compile javascript using V8 engine as opposed to interpreting.
  3. Introduce new virtual machine to support javascript heavy apps
  4. introduce "hidden class transitions" and apply dynamic optimization to speed up things.
  5. Replace inefficient "Conservative garbage colllection" scheme with more precise garbage collection scheme.
  6. Introduce their own task scheduler and memory manager to manage the browser environment.

All this sounds so familiar, and Microsoft has been doing such things for long time.. Windows os, C++, C# etc compilers, CLR, and so on.

So why isn't Microsoft or any other browser vendor taking Chrome's approach? Is there a flaw in Chrome's approach? If not, is the rest of browser vendor community caught unaware with Google's approach?

google-chrome
Edit
Report

2 Answers

3

IE8 uses a similar individual process per tab module, though they do not use a single process per tab, but instead spread all tabs across a process pool.

answered 2008-09-04T01:38:16.487
0

@pix0r but they added a little thing in the bottom right corner so you can expand the text box any direction you want, which I love because I use a wide display and prefer to type in a wider screen.

I also wanted to point out that Google completely built Chrome from the ground up, with the exception of using webkit, so they have some of the advantages of not having to not deal with old-code. And of course there is the INSANLELY cool/smart developers.

answered 2008-09-04T03:34:22.370

Your Answer