IE10 preview 3 supports HTML5 history API, CSS animations and 3D transforms
msdn.microsoft.com
msdn.microsoft.com
Whilst Google can get a really high percentage of users onto the latest version of Chrome within days, Microsoft cannot do the same with IE9 (and IE10 when it comes out).
The problem is, upgrading Windows (any OS, really) is so fraught with complexity (and spending) that most people and IT organizations would rather stay on a nice, stable Windows (i.e. XP) and deal with the older software. (Especially nontechnical people who just have Win XP because that's what came on their computer.) Unfortunately, that means the developers have to pay for it.
You can do some pretty nice things with 3d transforms. I've done some nice things anyways :)
We'll see what happens once webgl gets into mobile safari. Perhaps lots of people will use it, and then MS might be convinced that all that work is worth it.
On html5test.com IE9 still seems to score about half as any other Windows browser, so hopefully IE10 will try to catch-up with them in more HTML5 functionality. They say they want to support HTML5 but so far they are supporting it the least.
Also, I want to know how other browsers can work in the tile-based interface in Windows 8, hearing how its interface is based on IE10? Will they even allow other browsers in there, or will they risk an anti-trust lawsuit over the browser, again?
For all the talk about supporting the cross-platform web, Microsoft is still trying to lock it down to their own OS.
John Carmack: "I agree with Microsoft’s assessment that WebGL is a severe security risk. The gfx driver culture is not the culture of security."
http://twitter.com/#!/ID_AA_Carmack/status/81732190949486592
Security risks can be overcome. The implementation can overcome risk, as Chrome and Firefox's secure implementations prove. So the fact the risk exists is not a complete justification for not supporting the feature at all.
Given that it conflicts with Microsoft's strategy anyway, the conclusion is the security concerns are used as an excuse rather than a reason.
And it doesn't even seem like a lot of people are actively leaning on Chrome and Firefox's WebGL implementations, so calling them "secure" seems a little premature.
https://blogs.msdn.com/b/ie/archive/2011/04/12/native-html5-...
Edit: Just realized that there was in fact more info on the file API on that very page. The answer seems to be yes.
But we've built IE toolbars successfully using C#, which at the very least is head and shoulders better than C++.