4 ms·
It's not a question of how good you can get. (You do know what a prisoner's dilemma is, right?) It's a question of many developers having to devote man-hours to
by walterk 18y ago
It's not a question of how good you can get. (You do know what a prisoner's dilemma is, right?) It's a question of many developers having to devote man-hours to (1) learning how to support IE6 and (2) implementing that support for every new site design, of the money continually being spent to pay for that support, and of the inferior user experience to IE6 users. This is time and money effectively wasted, the aggregate cost of which exceeds the aggregate cost of IE6 users upgrading/switching browsers.
The longer we have to support IE6, the greater the cost.
- edw519 18y agoimplementing that support for every new site design If that's what you're doing, then you do have a problem. How can you deliver content to IE6 users, irregardless of site, without "implementing that support for every new site design"? Find an elegant answer to this question and change the way you do business. (You do know what a tradeoff override is, right?)
- walterk 18y agoDo you have a universal drop-in solution that you'd like to share? If so, then it renders the IE6 issue moot. If, on the other hand, you're expecting every developer to discover this solution themselves, then you're only proving my point.
- bradgessler 18y agoI would argue that the cost of support and the inferior user experience have not exceeded the cost of IE6 users upgrading/switching browsers. If that were the case, this thread wouldn't exist. That said, I hate IE6 as much as the next guy...