Where is the chink in Google Chrome's armor?
Posted
by kudlur
on Stack Overflow
See other posts from Stack Overflow
or by kudlur
Published on 2008-09-04T00:26:55Z
Indexed on
2010/04/12
17:43 UTC
Read the original article
Hit count: 232
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
- tabs are hosted in process rather than thread.
- compile javascript using V8 engine as opposed to interpreting.
- Introduce new virtual machine to support javascript heavy apps
- introduce "hidden class transitions" and apply dynamic optimization to speed up things.
- Replace inefficient "Conservative garbage colllection" scheme with more precise garbage collection scheme.
- 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?
© Stack Overflow or respective owner