4 ms·
I feel like whenever I read discussions about this on HN it's all about the JS engine. Chrome was on webkit but used V8. And unless something has changed all n
by maxmcd 12y ago
I feel like whenever I read discussions about this on HN it's all about the JS engine.
Chrome was on webkit but used V8. And unless something has changed all non-safari browsers and webviews use an inferior JS engine.
Edit: (Something has changed, WKWebView now has the Nitro JS Engine, cool beans)
- oscargrouch 12y agoAlso, when Chrome was launched, it was the only browser with a multi-process approach to a multi-tab browser world.. Also their approach to threads were right from the beginning, and that converge into a awesome no-lock and no-glitch browsing experience.. After that, every other browser followed them. So, to be fair, Chrome was much more than V8 (which was also a part of its voodoo)
- bgarbiak 12y agoAlso, when Chrome was launched, it was the only browser with a multi-process approach to a multi-tab browser world.. Nope, IE8 was: http://blogs.msdn.com/b/ie/archive/2008/03/11/ie8-and-loosely-coupled-ie-lcie.aspx http://blogs.msdn.com/b/ie/archive/2008/03/11/ie8-and-loosel...
- ClashTheBunny 12y agoChrome still crashes a few tabs for every process crash. And it feels random the ones that are threads of the same process.
- snotrockets 12y agoChrome's WebKit wasn't 100% compatible with Safari's WebKit. They released from different branches.