From 8d220627526f20c359e5d0399056d204aa43e489 Mon Sep 17 00:00:00 2001 From: Mikeal Rogers Date: Mon, 12 Jan 2015 13:19:54 -0800 Subject: [PATCH] Adding es6 pages. --- es6.html | 116 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ style.css | 13 ++++-- 2 files changed, 125 insertions(+), 4 deletions(-) create mode 100644 es6.html diff --git a/es6.html b/es6.html new file mode 100644 index 0000000..55ce0fd --- /dev/null +++ b/es6.html @@ -0,0 +1,116 @@ + + + + + + + + + Javascript IO - FAQ + + + + + +

ES6 on io.js

+ +
+ +

io.js is built against modern versions of V8. By keeping up-to-date with the latest releases of this engine we ensure new features from the JavaScript ECMA-262 specification are brought to io.js developers in a timely manner, as well as continued performance and stability improvements.

+

Version 1.0.0 of io.js ships with V8 3.31.71.4, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.

+
+ +
+ +

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.

+

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

+ +
    +
  • All shipping features, the ones that V8 has considered stable, like generators, templates, new string methods and many others are turned on by default on io.js and do NOT require any kind of runtime flag.
    • +
  • Then there are staged features which are almost-completed features that haven't been completely tested or updated to the latest spec yet and therefore are not considered stable by the V8 team (e.g. there might be some edge cases left to discover). This is probably the equivalent of the state of generators on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: --es_staging (or its synonym, --harmony).
    • +
  • Finally, all in progress features can be activated individually by their respective harmony flag (e.g. --harmony_arrow_functions), although this is highly discouraged unless for testing purposes.
    • +
+
+ +

+ Which ES6 features ship with io.js by default (no runtime flag required)? +

+
+ + +

You can view a more detailed list, including a comparison with other engines, on the compat-table project page.

+
+
+ +
+

+ Which ES6 features are behind the --es_staging flag? +

+
+ +
+
+ +
+ +

+ I have my infrastructure set up to leverage the --harmony flag. Should I remove it? +

+
+

The current behaviour of the --harmony flag on io.js is to enable staged features only. After all, it is now a synonym of --es_staging. As mentioned above, these are completed features that have not been considered stable yet. If you want to play safe, especially on production environments, consider removing this runtime flag until it ships by default on V8 and, consequently, on io.js. If you keep this enabled, you should be prepared for further io.js upgrades to break your code if V8 changes their semantics to more closely follow the standard.

+
+
+ +
+ +

+ How do I find which version of V8 ships with a particular version of io.js? +

+
+

io.js provides a simple way to list all dependencies and respective versions that ship with a specific binary through the process global object. In case of the V8 engine, type the following in your terminal to retrieve its version:

+ 
iojs -e 'console.log(process.versions.v8)'
+ +

E.g. output: 3.31.71.4.

+ +
+
+ +
+ +

+ How frequently do you plan on updating V8? +

+
+

A formal plan has not been discussed yet but the TC is looking into regular updates, especially if there are no breaking changes from V8's API.

+
+
+ + + diff --git a/style.css b/style.css index 256e8e4..84774a5 100644 --- a/style.css +++ b/style.css @@ -31,13 +31,13 @@ p { } a { text-decoration: none; - color: #2F2E2C; - border-bottom: 1px solid #2F2E2C; + color: #D3C132; + border-bottom: 1px solid #F8E233; transition: .3s all ease; } a:hover { - color: #aaa; - border-bottom: 1px solid #aaa; + color: #F7E133; + border-bottom: 1px solid #F8E233; } .button { border: solid 1px #2F2E2C; @@ -87,6 +87,7 @@ a:hover { } .faq-body { margin:1em; + text-align:left; } .brand { margin: 5px 10px; @@ -144,3 +145,7 @@ div.release-mac { margin: 0 0 0 0; padding: 1em; } + +div.description { + text-align:left; +}