Linked by Kroc Camen on Wed 16th Sep 2009 20:06 UTC
Sometime ago I conjectured that Microsoft made certain changes to IE8 to force web standards forward and drop backwards compatibility as default (a very un-Microsoft move) because of the need for the web to break out of the blinkered IE6 / Desktop-Browser view of content otherwise Microsoft would find itself unable to compete in the mobile space. It's been over a year since that article and in such a short period of time it has become ever clearer that Microsoft's mobile offerings, and their overall mobile platform strategy are failing against the dominant iPhone, the newcomer Android, and a re-invigorated Palm with WebOS.
Permalink for comment 384667
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-02
Microsoft would probably want to go in a different direction from the bulk of WebKit developers, so it's not likely that the code produced would be upstreamed very well... it would just be an increasingly divergent fork that would have to be maintained just as intensively as Trident currently is.
Adopting webkit makes sense if you literally have no existing engine. IE8 already contains big changes to Trident in the 'standards-mode' codepath, and IE9 will continue on this path.