Anyone here from MS care to explain why they continue to hold back the web and make us front end engineers work harder? Uggghh...
I am not from MS, but I can explain.
Most of their money comes, directly and indirectly, from selling Windows and Office licenses. Making the web functional enough that it would compete with desktop apps would lessen their lock-in and reduce their future revenue. IE has been, since its very first release, designed to fragment the web and to prevent it from becoming a viable applications platform. It and its matching development tools are designed to lure companies into writing IE-specific code, locking themselves into Microsoft ecosystem. That's why they are having difficulties getting rid of IE 6 and XP - it worked too well.
I am sure you were expecting their PR spin on this ;-) I am curious about what would it be.
First, don't attribute to malice what could better be explained by incompetence.
Second, isn't Ajax the most fundamental usability feature that allows web apps to compete with desktop apps?
And who created the XMLHttpRequest object?
Exactly.
Web sockets. Consider for a moment the issue with web sockets, and how the implementation was wrong, despite being put into browsers. Browsers had support for web sockets, and developers were developing for it. That obviously changed rather quickly.
Microsoft's idea is not to support things before they are relatively stable and supportable. Basically, their idea is if they put something into IE9, they aren't removing support.
That doesn't mean they aren't working on new features, nor are they preventing developers from adding it to their version of IE9 to test out the technologies. They call this "Site Ready". Basically, they feel the technology is ready for end users.
Now, I'm merely providing the information they are providing to developers. Do not argue with me.
Text-shadow and gradients would move design ahead in a good way. At least there are hacks, ms-filter cruft for text shadow and svg for gradients