And "giving up complete control"? We're only talking about the rendering engine, not the rest of the browser. And WebKit is open source, they can just fork it if MS is unhappy with where it is going.
I don't believe it's a lack of ability - Microsoft could easily produce a standard complaint browser. Adopting WebKit doesn't necessarily they would keep it compliant.
Given how important IE is to the Operating System in general, I doubt Microsoft could do this technically - not without breaking a raft of things... Given the incompatibility bumps with Vista I'll suspect they're would be seeking a more conservative path for the moment.
So why don't they? Is it to hold back the web so that they milk their desktop applications like Office a little bit more?
IE8 seems to be worse than the rest. Once again my site is broken in IE8. Just like it was in IE7 when that came out. They can't even keep the same basic functionality as previous versions.
If Microsoft had actually embraced the internet as a new exciting medium, instead of just releasing IE to kill off mozilla, perhaps they would have been one of the ones leading new development, instead of trailing hopelessly behind all the time.
I don't know what the answer is for IE, I can't see them giving up any control, they'll most likely muddle along with their own quirks and bugs while there's a slow but steady shift in users onto the new crop of browsers.
If Microsoft uses webkit, I'd like to think it's because they have realized that a consistent web browser experience from a developer point of view is enabling across the industry, not because they just want to leverage all the hardwork of other companies and open source developers just to get a leg up on their marketing. The last thing I want to hear is Microsoft marketing saying "We use Webkit, the same engine that powers other browsers like Apple's Safari" and the masses eating that up, but when we, as developers, know that isn't the case.