3 ms·
That is not my recollection. When Chrome debuted, some people had bazillion of FF extensions that were bogging it down, installed an extension-free Chrome, and
by toyg 8y ago
That is not my recollection. When Chrome debuted, some people had bazillion of FF extensions that were bogging it down, installed an extension-free Chrome, and went "much speed so wow". Later Google started pushing JS performance.
It doesn't matter that much anyway - Google didn't make the difference by converting FF users, but by being better than Mozilla at pushing IE users to switch. Which, again, was not a technical issue at all. I would bet that 90% of those users never even tried FF. A lot of them installed Chrome on Windows so they could synchronize settings from their main device, i.e. an Android phone.
- tapoxi 8y agoV8 and multiprocess were a huge part of the original announcement comic: https://www.google.com/googlebooks/chrome/ https://www.google.com/googlebooks/chrome/ At the time I remember this was a huge performance gain on my machine with my workflow (dozens of tabs), since you could easily open up the Chrome Task Manager and see which tab was causing problems. It was also the first browser to make updates invisible, so I installed it on every family member's PC.