[kenjackson]

You don't have to support IE. Just like an iPhone developer doesn't have to support Android. Or an OS X developer doesn't have to support Windows. You give up some market share, but it's a standard tradeoff == more work vs more revenue?

There's nothing to be sad about, it's a decision we make everyday. If IE is so painful that the revenue is not worth it, then don't do it. We currently don't support OS X. I'm not sad when Apple ships a new version of OS X. I just know that the 10% of the market that they own is one that we won't support. I'm fine with that, and have been for a while now.

[damoncali]

Here's the light at the end of the tunnel: I have a bug tracking app, and can honestly say that IE is an insignificant part of my traffic - comparable to Opera. Granted, it's a technical audience, but I can safely just not support IE.

Our day is coming...

[teilo]

Right. Here's your sales pitch:

"Well, sir (or ma'am), your new website will only work with 'Modern' browsers."

"I see. And what is a 'Modern' browser?"

"Anything but IE."

"Ah. Nice meeting with you. I'll keep your quote in mind."

No IE support != less revenue. No IE support = no revenue.

[andrewheins]

I really don't want to have to start thinking of myself as a "Firefox Developer". If it surfs the web, be it desktop browser, mobile browser, screen reader, robot or even IE, it's part of my job as a web developer.

[WiseWeasel]

Doesn't mean I have to reward Microsoft's failures to keep up with standards with praise, or by abstaining from criticism. My life would be better if they just gave up at this point.