From ce508fefb5b4eb0972861b55f3b45ddc820b47e6 Mon Sep 17 00:00:00 2001 From: Rui Marinho Date: Wed, 21 Jan 2015 17:44:31 +0000 Subject: [PATCH] Update expected node 0.12 V8 version node@0.11.15 has been updated to V8 2.28, so it is expected for node@0.12 to be released with this version. --- public/es6.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/es6.html b/public/es6.html index f805161..09b9191 100644 --- a/public/es6.html +++ b/public/es6.html @@ -38,7 +38,7 @@

ES6 on io.js

No more --harmony flag

-

On joyent/node@0.12.x (V8 3.26), the --harmony runtime flag enabled all completed, staged and in progress ES6 features together, in bulk (with the exception of nonstandard/non-harmonious semantics for typeof which were hidden under --harmony-typeof). This meant that some really buggy or even broken features like proxies were just as readily available for developers as generators, 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. --harmony-generators), or simply enable all of them and then use a restricted subset.

+

On joyent/node@0.12.x (V8 3.28), the --harmony runtime flag enabled all completed, staged and in progress ES6 features together, in bulk (with the exception of nonstandard/non-harmonious semantics for typeof which were hidden under --harmony-typeof). This meant that some really buggy or even broken features like proxies were just as readily available for developers as generators, 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. --harmony-generators), or simply enable all of them and then use a restricted subset.

With io.js@1.x (V8 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features: