[grackle]

Thank you. Thank you so much for articulating this.

I'd like to add that historical site analytics should always be a factor in the web developer's decision to support IE6 or not - and in my experience, B2B companies almost always have 40+ percent of users still on IE6.

Yes, we all want IE6 to die. Yes, it makes life harder for us in the development community.

But telling a client that "you can save money on your website if we ignore IE6" is inherently disingenuous, unless your client is already a web technologies expert (and if they're outsourcing web development, I'm doubting that this is the case). Nine times out of ten, the client will jump on the cost-saving opportunity, you will avoid the hassle of developing for backwards compatibility, and you'll feel good for having just stabbed IE6 in the kidney. But when the client's site analytics say that 40% of the customer base is still on IE6 (and this is typical in my experience) then you'll be costing them FAR more in lost business than you'll be saving them in web development costs.

I hate IE6 too... but there's more to it than just the added cost of development - and as stated earlier, many users simply don't have a choice in the matter.