Skip to content
This repository was archived by the owner on Nov 21, 2018. It is now read-only.

Commit 2ef5564

Browse files
committed
Merge pull request #93 from seegno/support/update-1-0-3-v8-version
Update io.js V8 version to that in 1.0.3
2 parents 15c8d67 + a07e054 commit 2ef5564

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

es6.html

+2-2
Original file line numberDiff line numberDiff line change
@@ -31,15 +31,15 @@ <h1>ES6 on io.js</h1>
3131
<div class="description">
3232

3333
<p>io.js is built against modern versions of <a href="https://code.google.com/p/v8/">V8</a>. By keeping up-to-date with the latest releases of this engine we ensure new features from the <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">JavaScript ECMA-262 specification</a> are brought to io.js developers in a timely manner, as well as continued performance and stability improvements.</p>
34-
<p>Version 1.0.2 of io.js ships with V8 3.31.74.1, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/[email protected].</p>
34+
<p>Version 1.0.3 of io.js ships with V8 4.1.0.7, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/[email protected].</p>
3535
</div>
3636

3737
<div class="faq-item">
3838

3939
<h2 class="faq-title">No more --harmony flag</h2>
4040
<div class="faq-body">
4141
<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>
42-
<p>With [email protected] (V8 3.31+), all that complexity goes away. All harmony features are now logically split into three groups for <strong>shipping</strong>, <strong>staged</strong> and <strong>in progress</strong> features:</p>
42+
<p>With [email protected] (V8 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for <strong>shipping</strong>, <strong>staged</strong> and <strong>in progress</strong> features:</p>
4343

4444
<ul class="task-list">
4545
<li>All <strong>shipping</strong> features, the ones that V8 has considered stable, like <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*">generators</a>, <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings">templates</a>, <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object">new string methods</a> and many others are turned <strong>on by default on io.js</strong> and do <strong>NOT</strong> require any kind of runtime flag. </li>

0 commit comments

Comments
 (0)