That second graph is horrendously misleading. It does a pretty bad job of comparing the numbers between browsers.
Firefox finally passes IE6
11–20 of 48 posts
Re: Firefox finally passes IE6
#12I like the arstechnica pie chart at the bottom. I'm guessing a large percentage of their IE users are in fact tied in by office systems and such. I suppose it's a credence to a tech site that its readers are overwhelmingly tech-orientated compared to the widespread market.
As another data point, I admin some fairly popular sites that cater to enterprise users and we have a huge percentage of IE6 users. Far more than the "average" site and certainly more than Firefox.
Re: Firefox finally passes IE6
#13This is an unfair comparison. No single version of Firefox has greater marketshare than any single version of Internet Explorer. If you take all version of Firefox together, yes they do beat the oldest version of Internet Explorer still in wide usage, IE6, but that's comparing apples and oranges. Web developers still have to target multiple versions of Firefox, and Firefox 2.x supports fewer things than Firefox 3.x.…
I just had a massive issue developing for Firefox. I spend the better part of yesterday fixing a handful of CSS bugs. It still doesn't work perfectly. I'm not very happy with Gecko at the moment.
I asked a friend on Windows to test it and he showed me it on IE, crippled and appallingly broken. My advice was for him to find another web browser. I'm willing to make Firefox work but draw the line at IE.
Re: Firefox finally passes IE6
#14This is an unfair comparison. No single version of Firefox has greater marketshare than any single version of Internet Explorer. If you take all version of Firefox together, yes they do beat the oldest version of Internet Explorer still in wide usage, IE6, but that's comparing apples and oranges. Web developers still have to target multiple versions of Firefox, and Firefox 2.x supports fewer things than Firefox 3.x.…
I just had a massive issue developing for Firefox. I spend the better part of yesterday fixing a handful of CSS bugs. It still doesn't work perfectly. I'm not very happy with Gecko at the moment. I asked a friend on Windows to test it and he showed me it on IE, crippled and appallingly broken. My advice was for him to find another web browser. I'm willing to make Firefox work but draw the line at IE.
If you aren't developing for Firefox or IE, what are you developing for?
Re: Firefox finally passes IE6
#15That second graph is horrendously misleading. It does a pretty bad job of comparing the numbers between browsers.
That second graph looks as if no scaling choices were made and the person just randomly chose to put spacing in.
Re: Firefox finally passes IE6
#16I like the arstechnica pie chart at the bottom. I'm guessing a large percentage of their IE users are in fact tied in by office systems and such. I suppose it's a credence to a tech site that its readers are overwhelmingly tech-orientated compared to the widespread market.
There is an important lesson for web devs in that 2nd pie chart.
Browser usage is enormously variable depending on demographics. When you weigh the cost/benefit tradeoffs of cross-browser compatibility for your site it is critical that you understand the actual browser usage for your site, not just the internet at large.
On a mass-appeal website that pulls in a wide cross-section of worldwide internet users IE may be the majority browser, dominating everything else by a 3:1 margin, with IE6 as popular as firefox. For such a site it probably pays off to make sure your site not only works but works well and looks good in IE, even IE6. However, if you have a more tech focused site then things are dramatically different, likely firefox will be the overwhelmingly dominant browser, with IE a distant 2nd, 3rd, or 4th and IE6 usage just a tiny slice. In that scenario the excessive costs of making IE (let alone IE6) compatibility a first tier design priority become completely unjustified and you should probably care about how well your site works in IE6 about as much as you care about it working in Opera (which is probably not much).
Re: Firefox finally passes IE6
#17This is an unfair comparison. No single version of Firefox has greater marketshare than any single version of Internet Explorer. If you take all version of Firefox together, yes they do beat the oldest version of Internet Explorer still in wide usage, IE6, but that's comparing apples and oranges. Web developers still have to target multiple versions of Firefox, and Firefox 2.x supports fewer things than Firefox 3.x.…
>>the oldest version of Internet Explorer still in wide usage, IE6, but that's comparing apples and oranges.
Which is also the version with the most market share and the most problematic for web development, FF 2.x is only 1.14, I'm pretty sure most people focus only on the latest versions for FF/Safari.
Re: Firefox finally passes IE6
#18I'm looking at that first chart and noticing Chrome creep up on Safari... Anyone know if this got a leg up when Chrome started being offered by the Java updater?
Re: Firefox finally passes IE6
#19Earlier quoted context omitted.
I just had a massive issue developing for Firefox. I spend the better part of yesterday fixing a handful of CSS bugs. It still doesn't work perfectly. I'm not very happy with Gecko at the moment. I asked a friend on Windows to test it and he showed me it on IE, crippled and appallingly broken. My advice was for him to find another web browser. I'm willing to make Firefox work but draw the line at IE.
If you aren't developing for Firefox or IE, what are you developing for?
WebKit, the least bullshit rendering engine available, and also the only one you can realistically target narrowly (iPhone/Android/Pre/etc.).
Re: Firefox finally passes IE6
#20Earlier quoted context omitted.
I just had a massive issue developing for Firefox. I spend the better part of yesterday fixing a handful of CSS bugs. It still doesn't work perfectly. I'm not very happy with Gecko at the moment. I asked a friend on Windows to test it and he showed me it on IE, crippled and appallingly broken. My advice was for him to find another web browser. I'm willing to make Firefox work but draw the line at IE.
If you aren't developing for Firefox or IE, what are you developing for?
I develop initially for Webkit, in part because Coda offers a built-in Webkit preview that makes coding for it very fast and easy. Then I preview it in Opera and Firefox.
I wish every web browser would switch to WebKit. It pains me how bad certain rendering engines are.