I thought the complaining that Microsoft wasn't using WebKit to be hilarious in light of Google's forking WebKit -- if Google and Apple couldn't collaborate on

I thought the complaining that Microsoft wasn't using WebKit to be hilarious in light of Google's forking WebKit -- if Google and Apple couldn't collaborate on WebKit development, there's no reason to suspect that Microsoft and Apple (or Microsoft and Google, in the case of Blink) would be able to collaborate any better. Meanwhile, Mozilla no longer allows embedded Gecko, and warns that doing so will mean not getting the latest security fixes: https://developer.mozilla.org/en-US/docs/Gecko/Embedding_Mozilla/FAQ/Embedding_Gecko https://developer.mozilla.org/en-US/docs/Gecko/Embedding_Moz... And now that Edge is close to release, we see that it already surpasses WebKit in HTML5 support: http://html5test.com/compare/browser/chrome-43/firefox-38/ie-Edge/safari-8.0.html http://html5test.com/compare/browser/chrome-43/firefox-38/ie... On the JavaScript side of things, Edge is tied for Firefox as the leading implementer of ES6 features: http://kangax.github.io/compat-table/es6/ http://kangax.github.io/compat-table/es6/ For a long time, Microsoft made a strategic decision to ignore the web, and that hurt a lot of things. And Microsoft has privileged archaic Intranet sites over progress on the web ever since, which hasn't been great either (unless you run one of those Intranet sites). But the idea that Microsoft doesn't have the resources to maintain a browser engine is ludicrous -- they're Microsoft. And they're already ahead of one of the suggested alternatives, WebKit. (And WebKit is probably the one of the three that's least tied to a specific browser implementation, so it's the one most amenable to having been picked in place of their Trident revamp.)