3 ms·
async/await is not in the ECMA spec. It a proposal, like Object.observe(which was discarded) And remember one thing, Nodejs maintainers DO NOT control V8, the j
by aikah 11y ago
async/await is not in the ECMA spec. It a proposal, like Object.observe(which was discarded) And remember one thing, Nodejs maintainers DO NOT control V8, the javascript engine powering it, they are entirely dependent on what the V8 team at Google does.
So you'll have to wait a long time and even so there is absolutely no guarantee async/away will ever make it to the spec. Same deal for decorators, developers shouldn't depend on non ECMA features. Even worse, the final proposal might be totally different from the current Babel/whatever implementation.
V8 doesn't even implement 100% of ES6, yet.
- vdaniuk 11y agoMicrosoft's Chakra engine is available as an alternative backend for node (windows only at the moment) and has native support of async/await. https://github.com/nodejs/node-chakracore https://github.com/nodejs/node-chakracore
- iends 11y agoDoes it still only run on Windows?
- vdaniuk 11y agoAFAIK linux and mac release is coming later this year and even then it won't have JIT support.
- hiteshk_msft 11y agoFor now. The Linux branch of ChakraCore is under active development. Disclaimer: working at Msft on ChakraCore
- ilkkao 11y agoStage 4 requires two working implementations. V8 could be the second one. No feature can reach stage 4 if it would be this strict as you describe.