>>>>> you need to develop a special site just for IE.
>>>>
>>>>That statement had a fair amount of merit up through IE7.
>>>>
>>>>I develop web database applications as my primary job - Using IE9 and 10 in standards mode makes them work at least as well as they do in Chrome. Firefox seems to lag farther behind with each release.
>>>>
>>>>We take cross browser compatibility seriously. Our apps run in IE and Chrome seamlessly before they go out for testing. Aside from a few minor CSS differences, we have no issues developing apps that work in both w/o any special handling.
>>>
>>>Its nice to know they implemented html4.1 right finally.
>>>
>>>I don't even test or support html5 in IE. There's no point.
>>
>>I don't test or support HTML5 in anything. I'll wait until 2014 when HTML5 standard is complete. I don't base business app on beta/test versions of software or standards.
>
>
>AMEN! If you are a responsible developer, using a tool that is not based upon a released standard is risky, and not professional.

In general I agree completely with you and Bill about this. In this case I think it is mitigated by the W3C being famously slow moving. I don't think anyone expects the HTML5 standard to change in any substantial way between now and final ratification. All the major browser vendors already support it. If they'll take that chance, so would I.