IE6 sucks, blah blah, I get it. I still don't think there's any excuse for a web designer to ship a product that doesn't work with IE6. If its a truly huge web app, OK. But for most sites it shouldn't take a good dev more than an hour to fix any IE6 bugs.
Instead, I take an Ellis Island approach: come as you are. If you want to buy my product, I'm going make sure that happens, and no IE6 bug is going to get in the way.
You're either setting the bar way too high for 'a good dev', or you're just unaware of how painful and bizarre IE6 bugs can be. Honestly, why would web devs just arbitrarily hate IE6 if it only took an hour to fix all the bugs for an entire website? You're positing a level of laziness and spite on the part of web devs which is just absurd.
Didn't mean to offend, and maybe I am setting the bar to high. I'm certainly aware of how bizarre IE6's bugs can be, but that doesn't make them especially difficult to fix.
Take for example the double float margin bug, which is undoubtedly one of the weirdest and most common. I definitely spent an entire afternoon on that one the first time I encountered it, and I wanted to throw my machine out the window, but now I know to add display:inline to anything I float that also has a margin. Its inane, but its not a big deal.
My point is that after a year or so, you've encountered all the annoying IE6 bugs, and so fixing them is easy. I don't think that's a particularly high bar.
Honestly, why would web devs just arbitrarily hate IE6 if it only took an hour to fix all the bugs for an entire website?
Its still an hour we shouldn't have to be spending, and I'm not saying I don't hate IE6. Hating IE6 is fine, and when a group of web guys gets together for a beer, its a great subject of ridicule. But its our problem, not our client's, and not our end user's.
Instead, I take an Ellis Island approach: come as you are. If you want to buy my product, I'm going make sure that happens, and no IE6 bug is going to get in the way.