| I'd be surprised if any of those, up to the last three, was a big deal for more than 1% or so of users. And I am inclined to think the original article probably has it right about simple saturation marketing as the cause of most user switching. But performance. Firefox very often outperforms Chrome in microbenchmarks and computationally-intensive code in my tests, but in the real world an awful lot of sites really are much more responsive in Chrome. For me as a user, most recently an update to the FastMail web UI a couple of weeks ago made it lamentably slow in Firefox -- just mousing over the folder tree caused CPU spikes and lag in updating -- and in the end I switched to opening FastMail in a separate Chrome instance while continuing to use Firefox for everything else. I've just switched it back to Firefox as I type this, to see whether anything has improved. The web app I'm working on as a developer just now also has problems updating as smoothly in Firefox as in Chrome, and I'm not at all sure whether we'll be able to do anything about it. I can't think of an example at the moment of a site that feels faster in Firefox. I believe I have come to think of Firefox as a web browser, and Chrome as a platform for web apps. Things written to be web apps are almost always more responsive in Chrome, even though many of their components (number-crunching work) really do run measurably quicker in Firefox. |