5 ms·

In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Node is going to get a serious boost of ES2015 features. Including but not limit

by inglor 11y ago

In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Node is going to get a serious boost of ES2015 features. Including but not limited to: Proper tail recursion (^_^) and destructuring. Tracked at http://node.green http://node.green We don't have an ES2015 features page up to date yet, but it's going to be ready any day now (and we're going to link to node.green anyway most likely).

ofrobots 11y ago
To be precise, Node.js 6.x will include V8 5.0. There has been a little discussion on being able to include V8 5.1 down the road, maybe, but there is nothing concrete on it at this point. Also, the fate for tail-call-elimination is pretty uncertain at the moment; see: https://github.com/tc39/proposal-ptc-syntax https://github.com/tc39/proposal-ptc-syntax
- richdougherty 11y ago
  :( I was looking forward to tail calls. As far as I can see WebKit/Safari is the only major browser that has an implementation: https://kangax.github.io/compat-table/es6/#test-proper_tail_calls_(tail_call_optimisation) https://kangax.github.io/compat-table/es6/#test-proper_tail_...
- inglor 11y ago
  Oh hi, fancy seeing you here :] Note that ptc syntax _ensures_ tail calls, tail calls themselves have _already_ been approved in ES2015 and are live in V8 (under a flag), you can follow their status here: https://bugs.chromium.org/p/v8/issues/detail?id=4698 https://bugs.chromium.org/p/v8/issues/detail?id=4698
westi 11y ago
FYI - Your https link generates a cert error because node.green is being served with the www.github.com ssl cert.
- inglor 11y ago
  Thanks! I've updated it to an http link, I'm just so used to https working everywhere nowadays. Maybe it's time to petition GH pages to support letsencrypt!
  - deanclatworthy 11y ago
    Or put the domain on cloudflare. My site is hosted on github too, with a CF cert. Works fine with https :)
    - inglor 11y ago
      Wouldn't that either cost money or only secure the connection from the client to cloudflare? From what I understand (and I admit, my knowledge is pretty lacking around what cloudflare offers) the free part is only the security between the client and cloudflare (and not the security between cloudflare and your server). On one hand it's better than nothing as I assume most MITMs are on local wifis and such but on the other it gives users a false sense of security. Then again none of this is of actual concern for node.green
      - bpicolo 11y ago
        It's a static site. Security between cloudflare and client seems like plenty
        paulddraper 11y ago
        client <-> cloudflare and cloudflare <-> server are the same.
        bpicolo 11y ago
        Not necessarily true in the case of government intervention
      - manojlds 11y ago
maga 11y ago
>In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Any info on when it is going to come out of that corner?
- ofrobots 11y ago
  The plan is for a Node.js 6.0 release on Tuesday: https://github.com/nodejs/node/issues/5766#issuecomment-198357402 https://github.com/nodejs/node/issues/5766#issuecomment-1983.... This would include V8 5.0.
  - maga 11y ago
    Wow, that's soon, thanks!
- mercer 11y ago
  For some reason the mismatched usage of 'corner' really bothers me! I'm sorry for this pointless comment.
  - idbehold 11y ago
    I was about to saw the same thing. That phrase must be so confusing for maga if he always pictures an interior corner instead of an exterior one.
    - maga 11y ago
      I'm sorry my humble attempt at wordplay mixing the corners bothers you, guys. You are right though, corners are not my forté: failed descriptive geometry back in engineering school.
      - mercer 11y ago
        Don't worry about it! I'm sure that from now on you'll avoid falling into this particular corner case of wordplay...
magicalist 11y ago
Proper tail calls are still behind a flag in V8 (including in the 5.2 version in current chrome canary). Is there any indication they'll be turned on by default in node 6?
fenomas 11y ago
Does anyone know if any ES2015 features are optimized yet? When last I checked, just having an unused `let` statement in a function made V8 bail out to the slow compiler, making ES2015 off-limits for anything nontrivial. But that was some months ago.
Bombthecat 11y ago
And by 2018 node will be as fast as php with 1,000 new features :)
cynx 11y ago
cool!
natorion 11y ago
ES2015 TCO is in 5.1 but hidden behind a flag. We are preferring the explicit approach championed by Mozilla and Microsoft (https://github.com/tc39/proposal-ptc-syntax https://github.com/tc39/proposal-ptc-syntax) because it makes the debugging and error analysis story better.

by inglor 11y ago

ofrobots 11y ago

To be precise, Node.js 6.x will include V8 5.0. There has been a little discussion on being able to include V8 5.1 down the road, maybe, but there is nothing concrete on it at this point. Also, the fate for tail-call-elimination is pretty uncertain at the moment; see: https://github.com/tc39/proposal-ptc-syntax https://github.com/tc39/proposal-ptc-syntax

richdougherty 11y ago
:( I was looking forward to tail calls. As far as I can see WebKit/Safari is the only major browser that has an implementation: https://kangax.github.io/compat-table/es6/#test-proper_tail_calls_(tail_call_optimisation) https://kangax.github.io/compat-table/es6/#test-proper_tail_...
inglor 11y ago
Oh hi, fancy seeing you here :] Note that ptc syntax _ensures_ tail calls, tail calls themselves have _already_ been approved in ES2015 and are live in V8 (under a flag), you can follow their status here: https://bugs.chromium.org/p/v8/issues/detail?id=4698 https://bugs.chromium.org/p/v8/issues/detail?id=4698

westi 11y ago

FYI - Your https link generates a cert error because node.green is being served with the www.github.com ssl cert.

inglor 11y ago
Thanks! I've updated it to an http link, I'm just so used to https working everywhere nowadays. Maybe it's time to petition GH pages to support letsencrypt!
- deanclatworthy 11y ago
  Or put the domain on cloudflare. My site is hosted on github too, with a CF cert. Works fine with https :)
  - inglor 11y ago
    Wouldn't that either cost money or only secure the connection from the client to cloudflare? From what I understand (and I admit, my knowledge is pretty lacking around what cloudflare offers) the free part is only the security between the client and cloudflare (and not the security between cloudflare and your server). On one hand it's better than nothing as I assume most MITMs are on local wifis and such but on the other it gives users a false sense of security. Then again none of this is of actual concern for node.green
    - bpicolo 11y ago
      It's a static site. Security between cloudflare and client seems like plenty
      - paulddraper 11y ago
        client <-> cloudflare and cloudflare <-> server are the same.
        bpicolo 11y ago
        Not necessarily true in the case of government intervention
    - manojlds 11y ago

maga 11y ago

>In case anyone is wondering, NodeJS v6 is right around the corner with V8 5.x. Any info on when it is going to come out of that corner?

ofrobots 11y ago
The plan is for a Node.js 6.0 release on Tuesday: https://github.com/nodejs/node/issues/5766#issuecomment-198357402 https://github.com/nodejs/node/issues/5766#issuecomment-1983.... This would include V8 5.0.
- maga 11y ago
  Wow, that's soon, thanks!
mercer 11y ago
For some reason the mismatched usage of 'corner' really bothers me! I'm sorry for this pointless comment.
- idbehold 11y ago
  I was about to saw the same thing. That phrase must be so confusing for maga if he always pictures an interior corner instead of an exterior one.
  - maga 11y ago
    I'm sorry my humble attempt at wordplay mixing the corners bothers you, guys. You are right though, corners are not my forté: failed descriptive geometry back in engineering school.
    - mercer 11y ago
      Don't worry about it! I'm sure that from now on you'll avoid falling into this particular corner case of wordplay...

magicalist 11y ago

Proper tail calls are still behind a flag in V8 (including in the 5.2 version in current chrome canary). Is there any indication they'll be turned on by default in node 6?

fenomas 11y ago

Does anyone know if any ES2015 features are optimized yet? When last I checked, just having an unused `let` statement in a function made V8 bail out to the slow compiler, making ES2015 off-limits for anything nontrivial. But that was some months ago.

Bombthecat 11y ago

And by 2018 node will be as fast as php with 1,000 new features :)

cynx 11y ago

cool!

natorion 11y ago

ES2015 TCO is in 5.1 but hidden behind a flag. We are preferring the explicit approach championed by Mozilla and Microsoft (https://github.com/tc39/proposal-ptc-syntax https://github.com/tc39/proposal-ptc-syntax) because it makes the debugging and error analysis story better.