Update io.js v1.1.0 and node v0.12.0 V8 versions #98

ruimarinho · 2015-01-21T17:47:05Z

[email protected] -> V8 4.1.0.14
[email protected] -> V8 3.28.73

Closes #124.

ruimarinho · 2015-01-21T20:36:16Z

@domenic do you have a chance to review this?

domenic · 2015-01-21T20:44:21Z

I never understood why were were comparing to a hypothetical future Node 0.12 release anyway. We should just compare to the latest stable, 0.10.35.

Fishrock123 · 2015-01-21T21:29:59Z

I agree with domenic.

therebelrobot · 2015-01-21T21:45:18Z

👍 to @Fishrock123 and @domenic

ruimarinho · 2015-01-21T22:46:01Z

Well, I guess it was due to the fact that the last V8 upgrade on the node 0.10 branch was done such a long time ago (one and a half years ago to v3.14.5.9) that it didn't sound like a fair comparison at the time of writing. 0.11.15 is supposed to be the RC version of 0.12, but who knows how many more months will it take for that to happen.

I'm fine with targeting the content for 0.10.35 and it seems like we already have two +1's from Collaborators too, so I'll go ahead and search the internet archives for V8 v3.14 :-).

@domenic, on a side note, I've noticed that 0.11.15 is shipping with V8 3.28.73 which is currently an abandoned version (the branch head of 3.28 is 3.28.71.19). Do you think it's worth to file that in?

domenic · 2015-01-21T22:59:27Z

Do you think it's worth to file that in?

Not sure what "file that in" means?

ruimarinho · 2015-01-21T23:00:41Z

To submit an issue to joyent/node's repository.

domenic · 2015-01-21T23:05:40Z

Oh. Shrug. My cares about joyent/node have plummeted to absolute zero.

ruimarinho · 2015-01-22T01:36:26Z

So V8 3.14 does not have any ES6 feature completed, so it seems pointless to compare io.js with [email protected] with the --harmony since literally no one is using that. However, [email protected] with the --harmony flag is commonly used (even in production) due to the support for generators that ignited projects and communities like koa and co.

What do you think about adding a small paragraph about [email protected]'s V8 version (for comparison) but keep [email protected]'s info without references to 0.12?

domenic · 2015-01-22T01:46:08Z

So V8 3.14 does not have any ES6 feature completed, so it seems pointless to compare io.js with [email protected] with the --harmony since literally no one is using that.

Agreed. It's more useful to compare io.js to node.js. io.js has ES6 features, and node.js does not.

What do you think about adding a small paragraph about [email protected]'s V8 version (for comparison) but keep [email protected]'s info without references to 0.12?

I might keep something very minimal, without mentioning versions at all. E.g., "If you ever used the unstable Node 0.11.x series with the --harmony flag, you'll notice this is very different behavior."

mgol · 2015-02-07T02:28:27Z

So, Node.js 0.12 has been released; it contains v8 3.28.73 (why is there the 4th number in the version missing?...). This PR should be modified to say shipped instead of will be shipped and merged.

mikeal · 2015-02-07T02:31:29Z

well, Joyent didn't write up anything about the ES6 features now available in the 6 month old version of v8 they shipped so someone would have to manually figure that out in order to write a comparison :(

mgol · 2015-02-07T02:34:11Z

I'll go ahead and search the internet archives for V8 v3.14

@ruimarinho You probably don't need it now that Node 0.12 has been released but it's 3.14.5.9 (the branch that landed in Chrome 24).

It's easy to check if you use nvm. :)

$ nvm exec 0.10 node -p process.versions.v8
Running node v0.10.36
3.14.5.9

(to install Node 0.10: nvm install 0.10)

mgol · 2015-02-07T02:35:24Z

well, Joyent didn't write up anything about the ES6 features now available in the 6 month old version of v8 they shipped so someone would have to manually figure that out in order to write a comparison :(

Yeah, weird. :/ However, as far as I understand it should more or less match Chrome 38. In particular, it doesn't have generators.

snostorm · 2015-02-07T02:43:11Z

In general we should address 0.12 dropping in a few ways through the product/public relations. That long-awaited release is going to gain a lot of press itself and possibly create some confusion. "Well, io.js is only based on v0.10... but the new Node.js™ is based on v0.11!"

Hmmm, this aspect should be a new issue/discussion. Anyway, re: the version, lets get this PR update or an alternative one to start addressing this specific development.

mgol · 2015-02-07T02:48:25Z

@snostorm Sure. However, what's currently on the site is incorrect and v8 3.28 is still putting most unfinished stuff behind --harmony:

  --harmony (enable all harmony features (except proxies))
        type: bool  default: false

contrary to io.js's v8 version:

  --harmony (enable all completed harmony features)
        type: bool  default: false

so most of the description should be correct besides version numbers. IMO v8 mentions should be updated on the site so that it's what we ended up with and the rest, public relations etc. can be discussed separately.

At least that's my humble opinion. :)

mikeal · 2015-02-07T02:52:47Z

Don't worry about the messaging side of it. I'm quite surprised at how little press 0.12 is getting at the moment (I have a theory about why that is and it will probably change on Tuesday).

As far as messaging, the differences between 0.12 and 0.10 are similar (outdated v8 and libuv). There are no improvements in 0.12 that are not in io.js and node.js is still lagging behind on shipping supported versions of its dependencies.

ruimarinho · 2015-02-07T17:57:41Z

I'm updating this now with the content from #124 as well. I was reluctant for more updates as the recent release cycle of 0.11.x was abnormal.

public/es6.html

    </div>

    <div class="faq-item">

      <h2 class="faq-title">No more --harmony flag</h2>
      <div class="faq-body">
-        <p>On joyent/[email protected] (V8 3.26), the <code>--harmony</code> runtime flag enabled all <strong>completed</strong>, <strong>staged</strong> and <strong>in progress</strong> ES6 features together, in bulk (with the exception of nonstandard/non-harmonious semantics for <code>typeof</code> which were hidden under <code>--harmony-typeof</code>).  This meant that some really buggy or even broken features like <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy">proxies</a> were just as readily available for developers as <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*">generators</a>, which had very little or even no known-issues. As such, it was best practice to either enable only certain features by using specific runtime harmony feature flags (e.g. <code>--harmony-generators</code>), or simply enable all of them and then use a restricted subset.</p>
+        <p>On joyent/[email protected] (V8 3.28), the <code>--harmony</code> runtime flag enabled all <strong>completed</strong>, <strong>staged</strong> and <strong>in progress</strong> ES6 features together, in bulk (with the exception of <code>proxies</code> which were hidden under <code>--harmony-proxies</code>). This meant that some really buggy or even broken features like <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions">arrow functions</a> were just as readily available for developers as <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*">generators</a>, which had very little or even no known-issues. As such, it was best practice to either enable only certain features by using specific runtime harmony feature flags (e.g. <code>--harmony-generators</code>), or simply enable all of them and then use a restricted subset.</p>


ruimarinho · 2015-02-08T04:11:26Z

Rebased and updated with the new V8 versions for both io.js 1.1.0 and node 0.12.0. I also double-checked that the features enabled via the --es_staging flag on io.js continue to be up-to-date (no changes), as well the shipping features (no changes too).

ruimarinho · 2015-02-08T04:17:26Z

Interestingly, though, they've shipped 0.12 with an unsupported V8 version, considering the branch head for 3.28 is actually sitting at 3.28.71.19.

PR-URL: #98

Fishrock123 · 2015-02-09T18:46:01Z

landed in 4486471 -- thanks!

ruimarinho force-pushed the support/update-node-v8-version branch from ce508fe to a012b06 Compare January 21, 2015 20:10

Fishrock123 added the content label Jan 21, 2015

domenic reviewed Feb 7, 2015
View reviewed changes

Rui Marinho added 2 commits February 8, 2015 03:57

Update io.js 1.1.0 and node 0.12 V8 versions

a64afd5

Replace joyent/node by Node.js™

35e07c1

ruimarinho force-pushed the support/update-node-v8-version branch from a012b06 to 35e07c1 Compare February 8, 2015 04:02

Update node --harmony description to present tense

36a8c58

ruimarinho changed the title ~~Update expected node 0.12 V8 version~~ Update io.js v1.1.0 and node v0.12.0 V8 versions Feb 8, 2015

Fishrock123 mentioned this pull request Feb 8, 2015

Update es6.html #124

Closed

Fishrock123 pushed a commit that referenced this pull request Feb 9, 2015

update comparison between io.js v8 and node 0.12 v8

4486471

PR-URL: #98

Fishrock123 closed this Feb 9, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update io.js v1.1.0 and node v0.12.0 V8 versions #98

Update io.js v1.1.0 and node v0.12.0 V8 versions #98

ruimarinho commented Jan 21, 2015

ruimarinho commented Jan 21, 2015

domenic commented Jan 21, 2015

Fishrock123 commented Jan 21, 2015

therebelrobot commented Jan 21, 2015

ruimarinho commented Jan 21, 2015

domenic commented Jan 21, 2015

ruimarinho commented Jan 21, 2015

domenic commented Jan 21, 2015

ruimarinho commented Jan 22, 2015

domenic commented Jan 22, 2015

mgol commented Feb 7, 2015

mikeal commented Feb 7, 2015

mgol commented Feb 7, 2015

mgol commented Feb 7, 2015

snostorm commented Feb 7, 2015

mgol commented Feb 7, 2015

mikeal commented Feb 7, 2015

ruimarinho commented Feb 7, 2015

This comment was marked as off-topic.

This comment was marked as off-topic.

ruimarinho commented Feb 8, 2015

ruimarinho commented Feb 8, 2015

Fishrock123 commented Feb 9, 2015

Update io.js v1.1.0 and node v0.12.0 V8 versions #98

Update io.js v1.1.0 and node v0.12.0 V8 versions #98

Conversation

ruimarinho commented Jan 21, 2015

ruimarinho commented Jan 21, 2015

domenic commented Jan 21, 2015

Fishrock123 commented Jan 21, 2015

therebelrobot commented Jan 21, 2015

ruimarinho commented Jan 21, 2015

domenic commented Jan 21, 2015

ruimarinho commented Jan 21, 2015

domenic commented Jan 21, 2015

ruimarinho commented Jan 22, 2015

domenic commented Jan 22, 2015

mgol commented Feb 7, 2015

mikeal commented Feb 7, 2015

mgol commented Feb 7, 2015

mgol commented Feb 7, 2015

snostorm commented Feb 7, 2015

mgol commented Feb 7, 2015

mikeal commented Feb 7, 2015

ruimarinho commented Feb 7, 2015

This comment was marked as off-topic.

This comment was marked as off-topic.

ruimarinho commented Feb 8, 2015

ruimarinho commented Feb 8, 2015

Fishrock123 commented Feb 9, 2015