> For the Edge browser Microsoft has again decided to develop their own rendering engine, instead of relying on open source alternatives (Blink, Gecko, WebKit). I have to doubt their decision as a browser engine is a big development effort and they need to be updating it from now to eternity. Um, why would they move when they already have an engine? Sure you can argue they should have moved to WebKit or Gecko or even…
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...
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/
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.)