I would assign much lower odds to the chances of it being less than $1000/yr worldwide, since I have personally done more than a day’s work on it in the last 12 months and our daily chargeable rate is higher than that.
Define wasted—I assume people generally put effort into making things work in IE because they expect to increase their audience as a direct result. For a profit making enterprise anyone investing time in making things work in IE is presumably doing so under the expectation that it will deliver a positive return. For a non-profit making enterprise the expectation is presumably that the increased audience is worth the expenditure based on whatever measure is used for the value of a larger audience.
Is your claim that people in fact consistently overestimate the return on investment for ensuring compatibility with IE? Or that relative to some hypothetical global optimum money is ‘wasted’? If the latter, how would you attempt to evaluate the waste?
What I intended by the word was simply that from an aggregate perspective, the optimal solution would be everyone, as matt said, using a good browser instead, which would require minimal effort by users, and make the time investment from developers unnecessary.
Still, I’ve edited to the more neutral spent.
ETA: I suppose if you wanted to put a dollar value to “time wasted”, you would have to subtract off the dollar value of the time it would take for each present-day IE user to download Firefox, Safari, Opera, Chrome, etc, import any bookmarks, and become familiar with its workings up to the level at which they were previously proficient in IE. This amount is non-negligible, and I was wrong to overlook it, but I strongly doubt that it is of the same order as the developer-time spent.
I’m curious, has anyone attempted to put a dollar amount to the developer time spent making things work in IE?
ETA: for Bayesian practice, I’ll put my 98% bars at...$1000/yr and $200000000/yr
I would assign much lower odds to the chances of it being less than $1000/yr worldwide, since I have personally done more than a day’s work on it in the last 12 months and our daily chargeable rate is higher than that.
Define wasted—I assume people generally put effort into making things work in IE because they expect to increase their audience as a direct result. For a profit making enterprise anyone investing time in making things work in IE is presumably doing so under the expectation that it will deliver a positive return. For a non-profit making enterprise the expectation is presumably that the increased audience is worth the expenditure based on whatever measure is used for the value of a larger audience.
Is your claim that people in fact consistently overestimate the return on investment for ensuring compatibility with IE? Or that relative to some hypothetical global optimum money is ‘wasted’? If the latter, how would you attempt to evaluate the waste?
I’m sorry, that was unclear.
What I intended by the word was simply that from an aggregate perspective, the optimal solution would be everyone, as matt said, using a good browser instead, which would require minimal effort by users, and make the time investment from developers unnecessary.
Still, I’ve edited to the more neutral spent.
ETA: I suppose if you wanted to put a dollar value to “time wasted”, you would have to subtract off the dollar value of the time it would take for each present-day IE user to download Firefox, Safari, Opera, Chrome, etc, import any bookmarks, and become familiar with its workings up to the level at which they were previously proficient in IE. This amount is non-negligible, and I was wrong to overlook it, but I strongly doubt that it is of the same order as the developer-time spent.
Does that include a dollar value assigned to volunteered coding time, or no?
Excellent question—I’d include the dollar value of whatever work the individual could have been doing, yes.