To view parent comment, click here.
To read all comments associated with this story, please click here.
While I agree that having one browser engine set the standards for the web is bad, it's certainly not comparable to the IE situation.
Anyone can implement Webkit, for free, that includes Microsoft.
That does not mean I like the idea of Webkit becoming a requisite for a fully functional web experience, particularly as I am not using webkit in my browsing (Firefox).
Everyone seems to be forgetting that Webkit and Trident are not the only two browser engines out there, and Trident is basically as single-platform as it gets so it's already limited. How about Gecko and Presto? And also the fact that Google has further explained the reasoning, claiming that IE for Windows Phone simply gave a poor experience?
Let's not forget that it's not even all of Trident that was not working... desktop versions of Windows Internet Explorer apparently worked fine, and were therefore unaffected. Perfectly understandable to me, and it comes to me as absolutely no surprise that a Trident-based browser would have trouble rendering something.
Move on. Google has already explained, is working to solve the problem if it hasn't been done already, and all it produced a day of whining. Like I said several times, Microsoft has done far worse themselves with absolutely no good excuse and without turning around over the course of a day.
Edited 2013-01-06 15:41 UTC





Member since:
2005-11-29
Its largely irrelevant if its poetic justice for Microsoft, it is detrimental to the web as a whole.
WebKit is as much as a threat to the web today as Microsoft was with IE back in the day.
And it really isn't WebKit's fault, they are victims of their own success and of the snails pace that the W3C moves at. This only serves to highlight a fundamental deficiency in this design by committee process.
Web developers really, largely, hold no allegiance. They will flock to whatever gives them the maximum coverage.
WebKit has a lot of functionality in vendor prefixed form, and using old implementations of recently updated specs. Again, a by product of the speed at which the W3C works.
Just as web developers naturally started developing for IE instead of for the web, the developers of today are targeting WebKit. On Mobile its defacto.
This normally wouldn't be an issue if the W3C didn't take 20 years for a standard because developers would have reasonably similar functionality across all of their browsers. But it does, and it is.
While Google's intent today may or may not have been malicious (I'll take their word that it was what they figured to be a sensible product decision), it does underscore a need to have a conversation about the state of the web.