if it wasn't enough to have google pushing it's weight around to drive new JS and html specs, now microsoft resurrects from the grave with out-of-IE6-history pearls such as:
"Legacy JSRT APIs ... Edge JSRT APIs"
when IE11 rolls out, lots of devs (obviously not in san francisco bubble) will be churning out sites that require IE11 new APIs to work.
let's just hope they at least bring something useful to justify the shitstorm, like they did with XMLHttpRequest (which does not get even the uppercase consistency right)
All of these apis seem to be exposed only when hosting the Chakra engine. They even call out the fact that it's not for in browser:
> However with JavaScript’s increasing popularity in beyond-the-browser scenarios, developers have been requesting to host the Chakra engine outside the browser to enable JavaScript programmability in their native/managed applications across the client and the server.
"Legacy JSRT APIs ... Edge JSRT APIs"
when IE11 rolls out, lots of devs (obviously not in san francisco bubble) will be churning out sites that require IE11 new APIs to work.
let's just hope they at least bring something useful to justify the shitstorm, like they did with XMLHttpRequest (which does not get even the uppercase consistency right)