3 ms·
Three existing production-ready open source engines + other embedded options wasn't already "competition"? It's nice to see but, as far as competition within
by nly 11y ago
Three existing production-ready open source engines + other embedded options wasn't already "competition"?
It's nice to see but, as far as competition within OSS is concerned, it's about 7-8 years too late. MS will no doubt, at some point, release something like Node.js based on this engine. If they do it'll be widely lauded, but you can barely say they're even a "fast follower" here when they're this slow.
- nailer 11y agoChakra does better than most of its competition on ES6 support: http://kangax.github.io/compat-table/es6/ http://kangax.github.io/compat-table/es6/ (I use v8 and javascriptcore all day but I still appreciate it)
- nly 11y agoTemporarily perhaps. Most of the gains look to have happened within the long IE11 to Edge 12 release cycle. Firefox 45 looks like it'll leap ahead again, and they're on a 6 week release cycle... I'm not disputing MS have made impressive efforts. I've just yet to see anything from them that would make me put long-term stock in their open source commitments.
- hirsin 11y agoChakra has been well ahead of the other browsers for >1 year now. That lead has been declining (as there's only so much of 100% you can implement), but kangax has always shown it to be ahead.
- simonw 11y ago"MS will no doubt, at some point, release something like Node.js based on this engine" https://github.com/Microsoft/node https://github.com/Microsoft/node - "This project enables Node.js to optionally use the Chakra JavaScript engine."