News for hackers. Stuff that matters.
Re:Browser Market Pollution: IE[x] is the new IE6 by pavel_lishin on Tuesday September 27, 2011 @01:07PM (#3044186)
> Meanwhile, you won't have to worry about supporting Firefox 6 or Chrome 13 in November.

You sure about that? Just because they're not officially supported doesn't mean a significant number of people won't still be using them.

Re:Browser Market Pollution: IE[x] is the new IE6 by bzbarsky on Tuesday September 27, 2011 @03:23PM (#3044804)
As of about a week ago, when Firefox 6 was the current release, the Firefox numbers looked like this (source is http://groups.google.com/group/mozilla.dev.planning/msg/d1d4... ):

  Firefox 5 is < 10% and dropping.
  Firefox 4 is < 5% and dropping.
Those are percentages of Firefox market share, not overall market share. So those correspond to somewhere around 2% and 1% of overall users respectively. Note that in November Firefox 6 will be in the position of Firefox 4 right now.

Also from the same post:

  The uptake curve got steeper between 5 and 6, which means
  more people are updating faster.
Re:Browser Market Pollution: IE[x] is the new IE6 by surrealize on Tuesday September 27, 2011 @05:33PM (#3045324)
"The uptake curve got steeper between 5 and 6, which means more people are updating faster."

You have to wonder how much of that is a selection effect. Since there was a change in the upgrade tempo in firefox, you'd expect to see the uptake curve get steeper even if overall user behavior hasn't changed, because the users that were on 5 when 6 came out would tend to be the more adventurous ones.

Edit: in other words, ff 5 didn't have as much time to accumulate less-adventurous users as ff 4 did, so the 5->6 transition will appear faster than the 4->5 transition.

Re:Browser Market Pollution: IE[x] is the new IE6 by bzbarsky on Tuesday September 27, 2011 @08:28PM (#3045902)
Yeah, that's a good question. It's hard to disentangle the effects given the available aggregate numbers. We'll see how things look going forward.
Re:Browser Market Pollution: IE[x] is the new IE6 by melling on Tuesday September 27, 2011 @01:16PM (#3044226)
Chrome 13 will definitely be gone. You can verify the data.

http://gs.statcounter.com/#browser_version-ww-monthly-201009...

Mozilla has more of a problem getting people to upgrade but I think they will if simply nudged.

Re:Browser Market Pollution: IE[x] is the new IE6 by gcp on Tuesday September 27, 2011 @01:23PM (#3044272)
>Mozilla has more of a problem getting people to upgrade but I think they will if simply nudged.

I'm guessing both Mozilla and the users are holding back a bit until they get more confident with the add-on situation.

Re:Browser Market Pollution: IE[x] is the new IE6 by nextparadigms on Tuesday September 27, 2011 @01:22PM (#3044269)
For Firefox it may take a few months since they don't do auto-updating like Chrome does, but almost everyone transitions to the latest version of Chrome in a matter of days.
Re:Browser Market Pollution: IE[x] is the new IE6 by bzbarsky on Tuesday September 27, 2011 @03:16PM (#3044778)
Firefox auto-updates. Where does this idea that it doesn't come from?
Re:Browser Market Pollution: IE[x] is the new IE6 by mappu on Tuesday September 27, 2011 @05:23PM (#3045292)
It auto-updates, yes, but not like chrome does.

Firefox downloads a ~15MB update that might cause unacceptably bad performance, or even not complete in an ordinary browsing session for users on slow connections.

Chrome downloads a assembly diff on the order of a few kilobytes, disassembles its own binary, patches and rebuilds on the client machine, completely transparently and without intervention of any sort.

Re:Browser Market Pollution: IE[x] is the new IE6 by bzbarsky on Tuesday September 27, 2011 @08:23PM (#3045889)
> Firefox downloads a ~15MB update

It depends on what you're updating. If you're updating from 3.6 to 4.0, across 18 months of work, then yes.

If you're updating from Firefox 6 to Firefox 7, say, then the update for Firefox on Windows is 6.5MB. The Mac updates are bit bigger because they're updating fat binaries. You can see for yourself at http://releases.mozilla.org/pub/mozilla.org/firefox/releases... -- the partial.mar is the update from 6.0.2 to 7.0.

> Chrome downloads a assembly diff on the order of a few > kilobytes

As of 2009, Chrome Courgette updates were about 80KB (compared to Chrome bsdiff updates of 700KB; bsdiff is what Firefox uses). This was for a total download of about 10MB.

At this point the total Chrome download size is a lot bigger; they have a lot more code; I would be surprised if their updates are smaller than 200KB. Or do you have data indicating otherwise?

One more thing. Courgette (Google's update tool) only works on x86 code last I checked. That may be one of the reasons they're not shipping a 64-bit Chrome even in environments where that's expected, like recent MacOS. And we'll see what happens when they port Chrome to ARM...

bsdiff, for all its faults, does not have those problems. Now 200KB is still a good bit smaller than 6MB. And I agree that for users on slow connections this can be a problem. That problem is becoming pretty rare in the US, Europe, an East Asia, though.