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

1.0.0 (Work in Progress, Releases on Jan 13th) #27

Merged
merged 26 commits into from
Jan 14, 2015
Merged

1.0.0 (Work in Progress, Releases on Jan 13th) #27

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
26 commits
Select commit Hold shift + click to select a range
a3586ff
Initial 1.0.0 work.
mikeal Jan 12, 2015
8d22062
Adding es6 pages.
mikeal Jan 12, 2015
907d8b6
Adding links to eventual resources.
mikeal Jan 13, 2015
97479c5
Fixing text color on hover.
mikeal Jan 13, 2015
5c7d88f
tweak styles, visual improvements
Fishrock123 Jan 13, 2015
914a84e
Merge branch 'master' of github.com:iojs/iojs.github.io into 1.0.0
mikeal Jan 13, 2015
f6fe71f
Merge branch '1.0.0' of github.com:iojs/iojs.github.io into 1.0.0
mikeal Jan 13, 2015
1f61e50
html and css juice cleanse
zeke Jan 13, 2015
85b736b
fix up the faq
zeke Jan 13, 2015
d66c7cd
protocol-relative fonts url
zeke Jan 13, 2015
c7acafc
add mobile styles
zeke Jan 13, 2015
b0d89cb
add 1.0.0 download to homepage
zeke Jan 13, 2015
b6935d4
use consistent markup on es6 page
zeke Jan 13, 2015
3247ac0
fixes, better link and nav styling
Fishrock123 Jan 13, 2015
cddc13c
cleanup, fixes, addresses some comments in #27
Fishrock123 Jan 13, 2015
0145510
nav: fix inline-block spacing
Fishrock123 Jan 13, 2015
b3da423
Going back to simpler messaging.
mikeal Jan 13, 2015
fdabf59
Fixing link.
mikeal Jan 13, 2015
1732823
Moves in-site nav links to header, adds docs link
snostorm Jan 13, 2015
f729806
header: improve spacing and styling
Fishrock123 Jan 13, 2015
8f8ccd6
re-add nightly releases link
Fishrock123 Jan 13, 2015
28a0e91
add governance link to faq & es6
Fishrock123 Jan 13, 2015
1ffb6e1
responsive - global: footer, index: download links
snostorm Jan 13, 2015
dbca2d8
responsiveness: Tightens padding on .content < 410px
snostorm Jan 13, 2015
8137e28
sets `<title>` to be based on content heading
snostorm Jan 13, 2015
44fb9f0
update dist and docs links
Fishrock123 Jan 14, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
116 changes: 116 additions & 0 deletions es6.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,116 @@
<!DOCTYPE html>
<html lang="en" class="faq">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="iojs">
<meta name="keywords" content="iojs, io.js, io js, javascript io, uv, libuv, node-forward, node forward, node, node.js, node.js forward, nodejs, nodejs forward, javascript">
<title>Javascript IO - FAQ</title>

This comment was marked as off-topic.

Sign in to view

<link href="style.css" rel="stylesheet" type="text/css">

</head>

<body>
<h1 class="heading">ES6 on io.js</h1>

<div class="description">

<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>
<p>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/[email protected].</p>
</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>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>

<ul class="task-list">
<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>

This comment was marked as off-topic.

Sign in to view

<li>Then there are <strong>staged</strong> 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 <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*">generators</a> on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: <code>--es_staging</code> (or its synonym, <code>--harmony</code>).</li>
<li>Finally, all <strong>in progress</strong> features can be activated individually by their respective harmony flag (e.g. <code>--harmony_arrow_functions</code>), although this is highly discouraged unless for testing purposes.</li>
</ul>
</div>

<h2 class="faq-title">
Which ES6 features ship with io.js by default (no runtime flag required)?
</h2>
<div class="faq-body">
<ul class="task-list">
<li>Block scoping</li>
<ul class="task-list">
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let">let</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const">const</a></li>
<li><code>function</code>-in-blocks (<a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode">strict mode only)</a></li>
</ul>
<li>Collections</li>
<ul class="task-list">
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map">Map</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap">WeakMap</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set">Set</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet">WeakSet</a></li>
</ul>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*">Generators</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals">Binary and Octal literals</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">Promises</a></li>
<li><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></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol">Symbols</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings">Template strings</a></li>
</ul>

<p>You can view a more detailed list, including a comparison with other engines, on the <a href="https://kangax.github.io/compat-table/es6/">compat-table</a> project page.</p>

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

</div>
</div>

<div class="faq-item">
<h2 class="faq-title">
Which ES6 features are behind the --es_staging flag?
</h2>
<div class="faq-body">
<ul class="task-list">

This comment was marked as off-topic.

Sign in to view

<li><a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/class">Classes</a> (strict mode only)</li>
<li><a href="http://wiki.ecmascript.org/doku.php?id=harmony:object_literals">Object literal extensions</a></li>

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

<li>
<a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol"><code>Symbol.toStringTag</code></a> (user-definable results for <code>Object.prototype.toString</code>)</li>
</ul>
</div>
</div>

<div class="faq-item">

<h2 class="faq-title">
I have my infrastructure set up to leverage the --harmony flag. Should I remove it?
</h2>
<div class="faq-body">
<p>The current behaviour of the <code>--harmony</code> flag on io.js is to enable <strong>staged</strong> features only. After all, it is now a synonym of <code>--es_staging</code>. 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.</p>
</div>
</div>

<div class="faq-item">

<h2 class="faq-title">
How do I find which version of V8 ships with a particular version of io.js?
</h2>
<div class="faq-body">
<p>io.js provides a simple way to list all dependencies and respective versions that ship with a specific binary through the <code>process</code> global object. In case of the V8 engine, type the following in your terminal to retrieve its version:</p>

This comment was marked as off-topic.

Sign in to view

<div class="highlight highlight-sh"><pre>iojs -e <span class="pl-s1"><span class="pl-pds">'</span>console.log(process.versions.v8)<span class="pl-pds">'</span></span></pre></div>

<p>E.g. output: <code>3.31.71.4</code>.</p>

</div>
</div>

<div class="faq-item">

<h2 class="faq-title">
How frequently do you plan on updating V8?
</h2>
<div class="faq-body">
<p>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.</p>

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

This comment was marked as off-topic.

Sign in to view

</div>
</div>

This comment was marked as off-topic.

Sign in to view

</body>
</html>
5 changes: 0 additions & 5 deletions faq.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,6 @@
</head>

<body>
<h2 class="brand">
<a href="index.html">
io.js
</a>
</h2>
<h1 class="heading">FAQ</h1>

<div class="faq-item">
Expand Down
Binary file added images/1.0.0.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
22 changes: 12 additions & 10 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,19 +12,21 @@
</head>

<body>
<h2 class="brand">
<a href="index.html">
io.js
</a>
</h2>
<h1 class="heading">JavaScript I/O</h1>
<h2>Bringing <a href="es6.html">ES6</a> to the Node Community!</h2>
<h2>
<a href="https://github.com/iojs/io.js"><code>io.js</code></a> is a JavaScript platform that is compatible with <a href="https://nodejs.org">Node.js</a> &amp; <a href="https://www.npmjs.org/">npm</a>.
<a href="https://github.com/iojs/io.js"><code>io.js</code></a> is an <a href="https://www.npmjs.org/">npm</a> compatible platform originally based on <a href="https://nodejs.org">node.js</a>&#8482;.
</h2>
<a href="https://github.com/iojs/io.js" class="button button-large">Coming soon...</a>
<p>
The initial 1.0.0 release <a href="https://github.com/iojs/io.js/issues/28">is planned</a> for January 13, 2015.
</p>

<div class="release">
<div class="release-logo"><img style="max-width:3em" src="images/1.0.0.png"></div>
<div class="release-stability">Beta</div>
<div class="release-date"><a href="">Jan 13th 2015</a></div>
<div class="release-source"><a href="">1.0.0.tgz</a></div>
<div class="release-windows"><a href="">Windows</a></div>
<div class="release-mac"><a href="">Mac</a></div>
</div>

<p>
<a href="https://iojs.org/download/nightly/">Nightly releases</a> are avaliable for testing.

This comment was marked as off-topic.

Sign in to view

</p>
Expand Down
77 changes: 63 additions & 14 deletions style.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,39 +15,39 @@ body {
display: inline-block;
max-width: 700px;
margin: 5px 6px;
background: #111;
color: #eee;
background: white;
color: #2F2E2C;
}
h1 {
font-size: 2em;
}
h2 {
font-size: 1.125em;
margin: 2.2em 0;
margin: 1em 0;
}
p {
font-size: 15px;
margin: .6em 0;
}
a {
text-decoration: none;
color: #eee;
border-bottom: 1px solid #eee;
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 #eee;
border: solid 1px #2F2E2C;
display: inline-block;
padding: 1em;
margin: 10px;
background-color: transparent;
border-radius: 3px;
transition: .3s all ease;
color: #eee;
color: #2F2E2C;
}
.button-large {
font-size: 20px;
Expand All @@ -56,7 +56,7 @@ a:hover {
border-radius: 5px;
}
.button:hover {
background-color: #eee;
background-color: #2F2E2C;
color: #333;

This comment was marked as off-topic.

Sign in to view

}
.multi-button {
Expand All @@ -69,24 +69,25 @@ a:hover {
.multi-button .button:first-child {
margin: 0;
border-radius: 3px 0 0 3px;
border: solid 1px #eee;
border: solid 1px #2F2E2C;
}
.multi-button .button:last-child {
border-radius: 0 3px 3px 0;
}
.faq-item {
border-radius: 3px;
border:solid 1px #eee;
border:solid 1px #2F2E2C;
margin:20px;
}
.faq-title {
margin:0;
line-height:3em;
background: #eee;
color:#333;
background: #2F2E2C;
color:white;
}
.faq-body {
margin:1em;
text-align:left;
}
.brand {
margin: 5px 10px;
Expand All @@ -100,3 +101,51 @@ a:hover {
font-size: 55px;
line-height: 175px;
}

/*releases*/

div.release {
/*border: solid 1px #2F2E2C;*/
display: inline-block;
padding: 0 0 0 0;
margin: 10px;
background-color: transparent;
border-radius: 3px;
transition: .3s all ease;
color: #2F2E2C;
font-weight:bold;
}
div.release-stability {
float:left;

This comment was marked as off-topic.

Sign in to view

padding: 1em;
border-right: solid 1px #2F2E2C;
border-left: solid 1px #2F2E2C;
}
div.release-date {
float:left;
padding: 1em;
border-right: solid 1px #2F2E2C;
}
div.release-logo {
float:left;
padding-right:1em;
}
div.release-source {
float:left;
padding: 1em;
border-right: solid 1px #2F2E2C;
}
div.release-windows {
float:left;
padding: 1em;
border-right: solid 1px #2F2E2C;
}
div.release-mac {
float:left;
margin: 0 0 0 0;
padding: 1em;
}

div.description {
text-align:left;
}