State of ES6/ES7 in node/v8?

[sathishsoundharajan]

I know this is not node question.. But want to know what community thinks..

Can I write a full application using current es6 features released with node?

Can I combine write es5 and es6. Will it lead to performance issues? Ex current node/v8 does not have es6 import/export. I can write a class but use module.exports to export. Does it affect anywhere?

If anyone did how was the performance?

I see some of them say native promises are slower, and performance of let===var.. Does this affect a web application? Is there any issues raised in v8 regarding this?

ES7-

I know many of us know Microsoft has added the experimental async and await feature in chakra..
That is awesome right?.. It will add some cleaner async operations.. Now that feature is added to stage 2 and may added stage 3 in near future.. Does anyone know when v8 gonna adds this and node gonna adapt? Timeline?

P.S: if this is not right place to ask this question.. Point me where I need to move.

Thanks

[Trott]

P.S: if this is not right place to ask this question.. Point me where I need to move.

These sorts of questions are better suited for the Node.js mailing list. Er, OK, see @mikeal's comments below instead.

[mikeal]

Never use the Node.js mailing list.

We have help repo now that is the best place for this kind of thing :) https://github.com/nodejs/help

[mikeal]

This details the features available in node from ES6 https://nodejs.org/en/docs/es6/

Unfortunately the question of "which features are performant" is an open one. We've been discussing writing another document about which ES6 features can be used in node.js core which would end up being a list of features that perform well but that isn't quite written yet.

None of "ES7" is implemented by V8 as none of the specs are done yet, and they are no longer called ES7 :)

Of course all of this is available through babel and in a few rare cases the babel compiler also optimizes parts of the code it spits out, but for the most part ES7 compiled down by babel will be a bit slower than code written directly for Node.js and not down compiled.

[sathishsoundharajan]

Thanks.. According to a comment on this issue nodejs/help#8. To use es6 fully using node core is gonna be by next year DEC 2016 ... That's 1.3 year from now.. Gonna stick with es5.... ES7 gonna take years to come on node.. & How are we calling ES7 ? :)

[sathishsoundharajan]

Just a thought.. If node does not tightly coupled with v8 we may have more features from spider monkey and chakra.. I see jx core is already doing it.. Does node team is going consider that? Is there any discussion regarding this.. I know it is overload and maintaince is difficult..

[mikeal]

v8 is still the "standard" vm, which means it's what you should expect people to run. if you're using features not in v8 and you're publishing that module to npm you're going to need to compile it down to something v8 can run.

[rocifier]

@bboysathish welp It's now December 2016 and you can basically make full use of ES6 in node.js =)
ES7 is called ES2016.