These number are <i>very</i> different than that shown by StatCounter [1] and Wikipedia [2]. If you look at Wikipedia's comparisons, they compare data from many sources. NetApplications (the dataset used by this article) is by far the one source that differs greatly from the rest of the data.<p>This likely has to do with the types of audiences that visit the sites they monitor, so the data should be taken with a grain of salt.<p>[1] <a href="http://gs.statcounter.com/" rel="nofollow">http://gs.statcounter.com/</a>
[2] <a href="http://en.wikipedia.org/wiki/Usage_share_of_web_browsers" rel="nofollow">http://en.wikipedia.org/wiki/Usage_share_of_web_browsers</a>
Two things:<p>1. I wish the author would define "market share" - is it % of users, percent of pageviews via that browser, or something else.<p>2. The adoption visualization really shows the difference between release strategies.
Chrome is still moving up on Clicky...<p><a href="http://getclicky.com/marketshare/global/web-browsers/" rel="nofollow">http://getclicky.com/marketshare/global/web-browsers/</a><p>I switched from Firefox to Chrome out of frustration because Firefox kept breaking the tree-style-tabs extension. I used to be a big Firefox defender before that but I gave up and moved to Chrome.
One thing I've noticed over the past year is that Chrome's automatic updates break functionality (OSX) and then Chrome needs to be restarted, but doesn't realize this and prompt the user to restart. Now whenever Chrome malfunctions I check for updates and 90% of the time an update was installed and is waiting for a restart.