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.1.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
+io.js 运行 ES6
+io.js 是基于 V8 引擎的现代版本构建的。通过持续更进最新版的 V8 引擎，我们确保可以及时为开发者带来最新的 JavaScript ECMA-262 规范 语言特性，同时也会有性能和稳定性的提升。
+io.js 1.2.0 集成了 V8 4.1.0.14 版本，其中包含的 ES6 特性远超出 joyent/node@0.12.x 集成的 3.26.33 版本。
+干掉 --harmony
+在 joyent/node@0.12.x (V8 3.26) 版本中，--harmony 运行时参数会一并开启所有 已完成，待完成 和 修订中 的 ES6 的一大堆特性 (除了 typeof 的非标准/不确定的特性需要通过 --harmony-typeof 开启之外)。这就意味着一些真正鸡肋甚至废弃的特性譬如 proxies 都会像 generators 那样开放给开发者，它们很偏门甚至缺少相关资料。因此，最好的做法要么通过加特定参数(例如 --harmony-generators) 开启稳定的特性，要么直接开启全部但严格地使用特定部分特性。
使用 io.js@1.x (V8 4.1+)，这些烦恼就通通没有了。所有的特性在逻辑上被分为 已完成，待完成 和 修订中 三部分：
-
-
- 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.
+ - 所有 已完成 的特性，都是在 V8 中确信已经稳定的，例如 generators，模板，新增的字符串方法等都会在 io.js 中默认开启 并且不需要加任何运行时参数。 +
- 再就是 待完成 的特性都是基本完成但是却没有经过充分测试或者更新为最新的标准，因此 V8 团队认为这些是不稳定的 (可能有些坑没被覆盖到)。相当于 generators 在 3.26版本中的状态。我们提供了类似 "自己承担使用风险" 的功能，需要加入运行时参数：
--es_staging(或者它的别名，--harmony)。
+ - 最后，所有 修订中 的特性可以通过特有的参数开启 (例如
--harmony_arrow_functions)，当然不建议这么做除非你是用于测试。
Which ES6 features ship with io.js by default (no runtime flag required)?
+io.js 默认开启了哪些 ES6 特性(不加任何参数)？
-
Block scoping
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
- - +
Which ES6 features ship with io.js by default (no runtime flag required)?Template strings
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?
+在 兼容列表 里可以看到更多详细内容和与其他引擎的对比。
+通过 --es_staging 参数开启的特性有哪些?
-
Classes (strict mode only)
@@ -108,10 +111,10 @@Which ES6 features are behind the --es_staging flag?
Symbol.toStringTag(user-definable results forObject.prototype.toString)
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:
我已经用了 --harmony 需要删除吗?
+当前 --harmony 参数在 io.js 中的行为是开启 待完成 特性。别忘了，它还有个别名 --es_staging。如上面提到的，这些待完成的特性还不稳定。如果想安全地使用，尤其是在生产环境中，最好删除此运行参数，直到特性被默认开启。因此，在 io.js 中。如果你现在保留了这个启用，也应该为以后进一步升级 io.js 做好准备，以备 V8 改为更加符合标准的语意。
如何找到某一版本的 io.js 所集成的 V8 的版本？
+io.js 提供了简单的方式列出所有依赖关系和各自的版本集成情况(基于 process 全局对象的特殊二进制文件)。例如要查看 V8 引擎版本，可以在你的终端里面输入以下命令获得：
iojs -p process.versions.v8
How do I find which version of V8 ships with a particular version of io.js?<
-->GitHub OrgIRC ChatLogsGovernance
+ -->项目管理
diff --git a/public/cn/faq.html b/public/cn/faq.html
index 6d92c81..e4aee65 100644
--- a/public/cn/faq.html
+++ b/public/cn/faq.html
@@ -26,31 +26,28 @@
- FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
-Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough
-to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback.
-Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is
-something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+ 常见问题
+io.js 是什么？
+io.js 是基于 Chrome's V8 运行环境 的 JavaScript 平台。本项目是在原 Joyent's Node.js™ 项目基础上继续开发，且兼容 npm 生态系统。
+想知道原因？io.js 旨在提供更快和可预测的发布周期。目前它融合了最新的语言特性，API，V8 引擎的性能改进并且会持续更新 libuv 和其他底层库。
+本项目旨在让大家在 "开放的管理模式" 下持续开发和维护 io.js 从而避免受制于公司或小团体。
+1.0.x 版本？
+io.js 已经转移到 Semver 而且 io.js 1.0.0 相对于 Node.js™ 0.10 版本的改进和差异已经足够升一个 major。
+我们的 v1.x 发布日志 列出了 相对于 Node.js v0.10.35 版本的所有改进。
+如何贡献？
+每个人都可以提供帮助。io.js 的 代码合并，贡献，发布都会在 开放的管理模式 下完成。
+开始使用前不妨看一下我们在 GitHub 上的讨论，我们很乐意听到你的反馈. 亲身参与讨论会让你更加感同身受，以后更是可以提供更多帮助。如果你有想法参与贡献的话，敬请 提交 pull request。
+此外，最好通过 Nodebug.me 帮助分担积压的问题。
+哪里讨论？
+在 Freenode IRC 上有一个 #io.js 频道。历史记录在 这里。
+什么是开源管理？
+开源项目管理提倡共同维护开源且开放的内容，以便所有想贡献的人都可以参与进来，譬如一个wiki文档。开放的规则对每一位开发者都是公平的，集体的智慧更有利于决策项目和共建一个更加民主的氛围。[来自 wikipedia]
diff --git a/public/cn/index.html b/public/cn/index.html
index 5c54deb..d52f65b 100644
--- a/public/cn/index.html
+++ b/public/cn/index.html
@@ -26,25 +26,24 @@
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
-
-Download for
-Linux,
-Win32, Win64,
-or
-Mac.
-
-Nightly releases are available for testing.
-
+为 Node 社区带来 ES6 ！
+io.js 是衍生于 node.js™ 并兼容 npm 的开发平台。
+
+
+下载
+Linux,
+Win32, Win64,
+Mac, 或 其他 版本。
+
+每日构建版本 可用于测试。
+
diff --git a/public/cs/es6.html b/public/cs/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/cs/es6.html
+++ b/public/cs/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/cs/index.html b/public/cs/index.html
index 5c54deb..5d496a5 100644
--- a/public/cs/index.html
+++ b/public/cs/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/da/es6.html b/public/da/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/da/es6.html
+++ b/public/da/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/da/index.html b/public/da/index.html
index 5c54deb..5d496a5 100644
--- a/public/da/index.html
+++ b/public/da/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/de/es6.html b/public/de/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/de/es6.html
+++ b/public/de/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/de/index.html b/public/de/index.html
index 5c54deb..5d496a5 100644
--- a/public/de/index.html
+++ b/public/de/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/el/es6.html b/public/el/es6.html
index afdf1bd..88d977c 100644
--- a/public/el/es6.html
+++ b/public/el/es6.html
@@ -28,13 +28,13 @@
FAQ
ES6
- API Docs
+ API
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
@@ -120,9 +123,9 @@ How do I find which version of V8 ships with a particular version of io.js?<
diff --git a/public/el/faq.html b/public/el/faq.html
index 6d92c81..df87a46 100644
--- a/public/el/faq.html
+++ b/public/el/faq.html
@@ -28,38 +28,37 @@
FAQ
ES6
- API Docs
+ API
FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
-Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough
-to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback.
-Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is
-something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+Τι σημαίνει io.js;
+io.js είναι μία JavaScript πλατφόρμα, βασισμένη στο V8 runtime του Chrome. Αυτό το πρότζεκτ ξεκίνησε σαν ένα fork του Node.js™ της Joyent, και είναι συμβατό με το οικοσύστημα του npm.
+Γιατί;
+Το io.js στοχεύει στο να παράσχει γρηγορότερες και πιο προβλέψιμες εκδόσεις. Αυτην την στιγμή, συγχωνεύει τις πιο πρόσφατες αλλαγές του V8 ως προς την γλώσσα, το API και τις βελτιώσεις στην απόδοση, ενώ παράλληλα προσφέρει αναβαθμίσεις από την βιβλιοθήκη libuv και άλλες βιβλιοθήκες.
+Το πρότζεκτ στοχεύει στην συνεχή ανάπτυξη του io.js, ύπο μία "ανοιχτή διακυβέρνηση" αντιθέτα από μία καθοδήγηση από κάποια εταιρία.
+Έκδοση 1.0.x;
+Το io.js πήγε σε Semver και οι αλλαγές μεταξύ Node.js™ 0.10 και io.js 1.0.0 είναι αρκετές για να υποστηρίξουν την αύξηση της κύριας έκδοσης (major version).
+Το ιστορικό αλλαγών για την v1.x παρέχει μία περίληψη των αλλαγών από το Node.js v0.10.35 στο io.js v1.0.x.
+Πως μπορώ να συνεισφέρω;
+Οποιοσδήποτε μπορεί να βοηθήσει. Το io.js υπακούει σε εναν κώδικα συμπεριφοράς, και οι συνεισφορές και εκδόσεις γίνονται με ένα μοντέλο "ανοιχτής διακυβέρνησης".
+Για να ξεκινήσετε, υπάρχουν ανοιχτές συζητήσεις στο GitHub, θα θέλαμε να ακούσουμε την γνώμη σας και τις απόψεις σας.
+Συμμετέχοντας στις συζητήσεις είναι ένας καλός τρόπος για να δείτε που και πως μπορείτε να βοηθήσετε το πρότζεκτ. Αν υπάρχει κάτι που θα θέλατε να προσθέσετε ή να βελτιώσετε, δημιουργήστε ένα pull request.
+Επίσης, χρησιμοποιώντας το Nodebug.me μπορείτε να λύσετε υπάρχοντα προβλήματα.
+Που γίνονται οι συζητήσεις;
+Υπάρχει ένα #io.js κανάλι στο Freenode IRC. Κρατάμε ιστορικό του καναλιού εδώ.
+Τι σημαίνει "ανοιχτή διακυβέρνηση";
+Η "ανοιχτή διακυβέρνηση" προωθεί τις αξίες του ανοιχτού κώδικα (open source) και του ανοιχτού περιεχομένου έτσι ώστε να μπορεί οποιοσδήποτε ενδιαφερόμενος να προσθέσει κάτι στην δημιουργία του τελικού αποτελέσματος, όπως σε ένα έγγραφο τύπου "wiki". Η νομοθεσία είναι δημοκρατικά ανοιχτή σε γενική κριτική έτσι ώστε να επωφεληθεί από τις γνώσεις όλων και να προωθεί την ιδέα της δημοκρατίας.
diff --git a/public/el/index.html b/public/el/index.html
index 5c54deb..2f2a04b 100644
--- a/public/el/index.html
+++ b/public/el/index.html
@@ -28,32 +28,33 @@
FAQ
ES6
- API Docs
+ API
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
-
-Download for
-Linux,
-Win32, Win64,
-or
-Mac.
-
-Nightly releases are available for testing.
-
+Φέρνουμε την ES6 στην κοινότητα του Node!
+io.js είναι μια πλατφόρμα συμβατή με το npm, βασισμένη στο node.js™.
+
+
+Κατεβάστε για
+Linux,
+Win32,
+Win64,
+Mac ή
+others.
+
+Nightly εκδόσεις είναι διαθέσιμες για testing.
+
diff --git a/public/en/es6.html b/public/en/es6.html
index 0121096..e6a01ce 100644
--- a/public/en/es6.html
+++ b/public/en/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.28.73 that ship with Node.js™ 0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.28.73 that ship with Node.js™ 0.12.x.
No more --harmony flag
On Node.js™@0.12.x (V8 3.28+), the --harmony runtime flag enables all completed, staged and in progress ES6 features together, in bulk (with the exception of proxies which are hidden under --harmony-proxies). This means that some really buggy or even broken features like Arrow Functions are just as readily available for developers as generators, which have very little or even no known-issues. As such, most developers tend to 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:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
@@ -99,15 +102,20 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Which ES6 features are behind the --es_staging flag?
-
-
Classes (strict mode only)
+Classes (strict mode only, behind flag --harmony_classes which implies block scoping & object literal extensions)
-
-
+
Object literal extensions (behind flag --harmony_object_literals)
-
-
Symbol.toStringTag (user-definable results for Object.prototype.toString)
+Symbol.toStringTag (user-definable results for Object.prototype.toString, behind flag --harmony_tostring)
+Which ES6 features are in progress?
+New features are constantly being added to the V8 engine. Generally speaking, expect them to land on a future io.js release, although timing is unknown.
+You may list all the in progress features available on each io.js release by grepping through the --v8-options argument. Please note that these are incomplete and possibly broken features of V8, so use them at your own risk:
+iojs --v8-options | grep "in progress"
+
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?
diff --git a/public/en/index.html b/public/en/index.html
index 3c2dfd2..e92c495 100644
--- a/public/en/index.html
+++ b/public/en/index.html
@@ -35,14 +35,14 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32,
-Win64,
-Mac or
-others.
+Linux,
+Win32,
+Win64,
+Mac or
+others.
Nightly releases are available for testing.
diff --git a/public/es/es6.html b/public/es/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/es/es6.html
+++ b/public/es/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/es/index.html b/public/es/index.html
index 4e60753..94cc790 100644
--- a/public/es/index.html
+++ b/public/es/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/es_AR/es6.html b/public/es_AR/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/es_AR/es6.html
+++ b/public/es_AR/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/es_AR/index.html b/public/es_AR/index.html
index 5c54deb..5d496a5 100644
--- a/public/es_AR/index.html
+++ b/public/es_AR/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/es_CO/es6.html b/public/es_CO/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/es_CO/es6.html
+++ b/public/es_CO/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/es_CO/index.html b/public/es_CO/index.html
index 5c54deb..5d496a5 100644
--- a/public/es_CO/index.html
+++ b/public/es_CO/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/es_ES/es6.html b/public/es_ES/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/es_ES/es6.html
+++ b/public/es_ES/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/es_ES/index.html b/public/es_ES/index.html
index 5c54deb..5d496a5 100644
--- a/public/es_ES/index.html
+++ b/public/es_ES/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/fr/es6.html b/public/fr/es6.html
index afdf1bd..e0137e6 100644
--- a/public/fr/es6.html
+++ b/public/fr/es6.html
@@ -28,13 +28,13 @@
FAQ
ES6
- API Docs
+ Doc de l'API
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
@@ -118,11 +121,11 @@ How do I find which version of V8 ships with a particular version of io.js?<
diff --git a/public/fr/faq.html b/public/fr/faq.html
index 6d92c81..6d8977c 100644
--- a/public/fr/faq.html
+++ b/public/fr/faq.html
@@ -28,38 +28,37 @@
FAQ
ES6
- API Docs
+ Doc de l'API
FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
+Qu'est-ce que io.js?
+io.js est une plateforme JavaScript construite sur le moteur d'exécution de Chrome's, V8. Ce projet a commencé comme un fork de Node.js™ de Joyent et est compatible avec l'écosystème npm.
+Pourquoi? L'objectif de io.js est de fournir des cycles de développement plus rapides et prévisibles. Il fusionne actuellement les dernières fonctionnalités du langage, API et améliorations de performance de V8 tout en mettant à jour libuv et d'autres bibliothèques de base.
+Ce projet vise à poursuivre le développement de io.js sous un "modèle de gouvernance ouvert" par opposition à la gérance de Node.js™ organisée par Joyent, jugée restreinte.
Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough
-to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback.
-Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is
-something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+io.js est passé à une gestion sémantique de version, Semver et les changements entre Node.js™ 0.10 et io.js 1.0.0 sont assez significatifs pour légitimer le passage à une nouvelle version majeure.
+Notre CHANGELOG pour la v1.x fournit un résumé des changements effectués entre Node.js v0.10.35 et io.js v1.0.x.
+Comment puis-je contribuer?
+Tout le monde peut aider. Io.js adhère à un code de conduite, et les contributions sont sous un modèle de gouvernance ouverte.
+Pour commencer, il y a des discussions ouvertes sur GitHub, et nous aimerons entendre votre avis.
+S'impliquer dans les discussions est un bon moyen pour savoir comment aider davantage. S'il y a
+quelque chose que vous vous sentez capable d'améliorer, créez une pull request.
+En outre, utiliser Nodebug.me est un bon moyen pour aider au triage des issues dans le backlog.
+Où les discussions ont-elles lieu?
+Il y a un canal de discussion IRC #io.js sur Freenode. Nous gardons les logs du canal ici.
+Qu'est-ce que la gouvernance open source?
+La gouvernance open source préconise l'application de la philosophie des mouvements open source et open content dans afin de permettre toute personne intéressée de contribuer à la création finale du produit, comme dans un document wiki. La législation est démocratiquement ouverte à l'ensemble des citoyens, employant leur sagesse collective afin d'en faire bénéficier le processus de décision et améliorer la démocratie. [source]
diff --git a/public/fr/index.html b/public/fr/index.html
index 5c54deb..db776ef 100644
--- a/public/fr/index.html
+++ b/public/fr/index.html
@@ -28,32 +28,32 @@
FAQ
ES6
- API Docs
+ Doc de l'API
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
-
-Download for
-Linux,
-Win32, Win64,
-or
-Mac.
+ES6 pour la communauté Node!
+io.js est une plateforme compatible avec npm et basée sur node.js™.
+
+
+Télécharger pour
+Linux,
+Win32, Win64,
+ou
+Mac.
-Nightly releases are available for testing.
-
+Les Nightly releases sont disponibles pour des tests.
+
diff --git a/public/he/es6.html b/public/he/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/he/es6.html
+++ b/public/he/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/he/index.html b/public/he/index.html
index 5c54deb..5d496a5 100644
--- a/public/he/index.html
+++ b/public/he/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/hi/es6.html b/public/hi/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/hi/es6.html
+++ b/public/hi/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/hi/index.html b/public/hi/index.html
index 5c54deb..5d496a5 100644
--- a/public/hi/index.html
+++ b/public/hi/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/hu/es6.html b/public/hu/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/hu/es6.html
+++ b/public/hu/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/hu/index.html b/public/hu/index.html
index 5c54deb..5d496a5 100644
--- a/public/hu/index.html
+++ b/public/hu/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/id/es6.html b/public/id/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/id/es6.html
+++ b/public/id/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/id/index.html b/public/id/index.html
index 5c54deb..5d496a5 100644
--- a/public/id/index.html
+++ b/public/id/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/it/es6.html b/public/it/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/it/es6.html
+++ b/public/it/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/it/index.html b/public/it/index.html
index 5c54deb..5d496a5 100644
--- a/public/it/index.html
+++ b/public/it/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/jp/es6.html b/public/jp/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/jp/es6.html
+++ b/public/jp/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/jp/index.html b/public/jp/index.html
index 5c54deb..5d496a5 100644
--- a/public/jp/index.html
+++ b/public/jp/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/ka/es6.html b/public/ka/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/ka/es6.html
+++ b/public/ka/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/ka/index.html b/public/ka/index.html
index 5c54deb..5d496a5 100644
--- a/public/ka/index.html
+++ b/public/ka/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/kr/es6.html b/public/kr/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/kr/es6.html
+++ b/public/kr/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/kr/index.html b/public/kr/index.html
index 5c54deb..5d496a5 100644
--- a/public/kr/index.html
+++ b/public/kr/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/mk/es6.html b/public/mk/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/mk/es6.html
+++ b/public/mk/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/mk/index.html b/public/mk/index.html
index 5c54deb..5d496a5 100644
--- a/public/mk/index.html
+++ b/public/mk/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/nl/es6.html b/public/nl/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/nl/es6.html
+++ b/public/nl/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/nl/index.html b/public/nl/index.html
index 5c54deb..5d496a5 100644
--- a/public/nl/index.html
+++ b/public/nl/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/no/es6.html b/public/no/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/no/es6.html
+++ b/public/no/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/no/index.html b/public/no/index.html
index 5c54deb..5d496a5 100644
--- a/public/no/index.html
+++ b/public/no/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/pl/es6.html b/public/pl/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/pl/es6.html
+++ b/public/pl/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/pl/index.html b/public/pl/index.html
index 5c54deb..5d496a5 100644
--- a/public/pl/index.html
+++ b/public/pl/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/pt_BR/es6.html b/public/pt_BR/es6.html
index afdf1bd..4e28eb6 100644
--- a/public/pt_BR/es6.html
+++ b/public/pt_BR/es6.html
@@ -28,25 +28,25 @@
FAQ
ES6
- API Docs
+ Documentação da API
- 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.1.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
+ ES6 no io.js
+O io.js é construído usando versões modernas do V8. Mantendo-nos atualizados com as últimas versões desta engine, garantimos que novas funcionalidades da especificação JavaScript ECMA-262 são trazidas para desenvolvedores io.js rapidamente, além de manter performance continuada e melhorias de estabilidade.
+A versão 1.2.0 do io.js vem com o V8 4.1.0.14, que inclui funcionalidades do ES6 bem além da versão 3.26.33 que vem com o joyent/node@0.12.x.
+Não mais flag --harmony
+No joyent/node@0.12.x (V8 3.26), a flag de runtime --harmony habilitava todas funcionalidades ES6 completas, em teste e em progresso juntas, de uma vez só (com a exceção de semânticas não padrão/não harmoniosas para typeof que estavam escondidas sob --harmony-typeof). Isto significava que algumas funcionalidades realmente bugadas ou mesmo quebradas como os proxies estavam prontamente disponíveis para desenvolvedores como os generators, que tinham poucos ou mesmo nenhuma issue conhecida. Portanto, era uma boa prática ou habilitar apenas certas funcionalidades usando flags de runtime harmony para funcionalidades específicas (por ex. --harmony-generators), ou simplesmente habilitar tudo e depois usar apenas um subconjunto restrito.
+Com o io.js@1.x (V8 4.1+), toda esta complexidade vai embora. Todas as funcionalidades harmony agora estão logicamente divididas em três grupos para funcionalidades entregues, sob testes e em progresso:
-- 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.
+- Todas funcionalidades entregues, aquelas consideradas estáveis pelo V8, como generators, templates, novos métodos de string e muitas outras são habilitadas por padrão no io.js e NÃO requerem qualquer tipo de flag de runtime.
+- Então há as funcionalidades em testes que são funcionalidades quase completas que não foram completamente testadas ou atualizadas com a última especificação e portanto não são consideradas estáveis pela equipe do V8 (por ex. pode haver alguns edge cases restando a descobrir). Isto é provavelmente o equivalente ao estado dos generators no 3.26. Estas são funcionalidades do tipo "use sob seu próprio risco" que agora requerem a flag:
--es_staging (ou seu sinônimo, --harmony).
+- Finalmente, todas funcionalidades em progresso podem ser ativadas individualmente pela sua respectiva flag harmony (por ex.
--harmony_arrow_functions). No entanto, isto é altamente desemcorajado a não ser para fins de teste.
-Which ES6 features ship with io.js by default (no runtime flag required)?
+Que funcionalidades ES6 estão disponíveis por padrão no io.js (sem requerer flag)?
-
-
Block scoping
+Escopo de bloco
-
@@ -55,15 +55,15 @@
Which ES6 features ship with io.js by default (no runtime flag required)?const
-
-
function-in-blocks
+function em blocos
-As of v8 3.31.74.1, block-scoped declarations are intentionally implemented with a non-compliant limitation to strict mode code. Developers should be aware that this will change as v8 continues towards ES6 specification compliance.
+Desde o v8 3.31.74.1, declarações em escopo de bloco são intencionalmente implementadas como uma limitação em não conformidade com código em modo estrito. Desenvolvedores devem estar cientes que isto deve mudar assim que o v8 continuar em direção à conformidade com a especificação ES6.
-
-
Collections
+Coleções
-
@@ -75,54 +75,57 @@
Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
-
+
-
-
+
+
+-
+
-
-
-
+
-
-
-
+
-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?
+Você pode ver uma lista mais detalhada, incluindo uma comparação com outras engines, no página do projeto da tabela de compatibilidade.
+Que funcionalidades ES6 estão sob a flag --es_staging?
-
-
Classes (strict mode only)
+Classes (modo estrito apenas)
-
-
+
-
-
Symbol.toStringTag (user-definable results for Object.prototype.toString)
+Symbol.toStringTag (resultados definidos pelo usuário para Object.prototype.toString)
-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:
+Eu tenho minha própria infraestrutura configurada para usar a flag --harmony. Devo removê-la?
+O comportamento atual da flag --harmony no io.js é para habilitar funcionalidades em testes apenas. Além disso, ela é agora um sinônimo de --es_staging. Como mencionado acima, estas são funcionalidades completas que não foram consideradas estáveis ainda. Se você quiser manter-se seguro, especialmente em ambientes de produção, considere remover esta flag de runtime até que ela seja disponibilizada por padrão no V8 e, consequentemente, no io.js. Se você mantê-la habilitada, você deve estar preparado para que futuras atualizações do io.js quebrem seu código se o V8 alterar suas semânticas para ter uma maior conformidade com a especificação.
+Como posso saber que versão do V8 está disponível com uma versão específica do io.js?
+O io.js fornece uma maneira simples de listar todas as dependências e suas respectivas versões que são disponibilizadas em um binário através do objeto global process. No caso da engine V8, digite o seguinte em seu terminal para obter sua versão:
iojs -p process.versions.v8
diff --git a/public/pt_BR/faq.html b/public/pt_BR/faq.html
index 6d92c81..f982f68 100644
--- a/public/pt_BR/faq.html
+++ b/public/pt_BR/faq.html
@@ -28,38 +28,36 @@
FAQ
ES6
- API Docs
+ Documentação da API
FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
-Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough
-to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback.
-Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is
-something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+O que é io.js?
+io.js é uma plataforma JavaScript construída no Chrome's V8 runtime. Esse projeto começou como um fork do Node.js™ da Joyent e é compátivel com o ecossistema npm.
+Por que? O io.js visa fornecer ciclos de release mais rápidos e previsíveis. Atualmente ele traz as últimas melhorias em linguagem, API e desempenho do V8 e ao mesmo tempo atualizando a libuv e outras bibliotecas base.
+Este projeto tem como objetivo continuar o desenvolvimento do io.js sob um "modelo de governança aberto" em oposição à administração corporativa.
+Versão 1.0.x?
+io.js passou a usar Semver e as mudanças entre o Node.js™ 0.10 e io.js 1.0.0 foram significativas o suficiente para justificar um grande incremento da versão.
+Nosso CHANGELOG para a v1.x fornece um resumo das alterações do Node.js v0.10.35 para o io.js v1.0.x.
+Como posso contribuir?
+Todos podem ajudar. O io.js adere a um código de conduta, e contribuições, lançamentos e autoria de contribuições estão sob um modelo de governaça aberta.
+Para começar, abra uma issue no GitHub, e nós vamos adorar ouvir seu feedback.
+Envolver-se em discussões é uma boa forma de ter uma sensação de que você pode ajudar ainda mais. Se houver algo que você sente que você pode resolver, por favor faça um pull request.
+Além disso, usar o Nodebug.me é uma boa forma de ajudar na triagem de issues no backlog.
+Onde as discussões acontecem?
+Há um canal #io.js no IRC Freenode. Nós mantemos os logs do canal aqui.
+O que é governança de código aberto?
+A governança de código aberto defende a aplicação das filosofias do Open Source e dos movimentos de conteúdo aberto, a fim de permitir que todos os interessados possam acrescentar à criação do produto final, como acontece com um documento Wiki. A legislação é democraticamente aberta aos cidadãos em geral, empregando sua sabedoria coletiva para beneficiar o processo de tomada de decisão e melhorar a democracia. [fonte]
diff --git a/public/pt_BR/index.html b/public/pt_BR/index.html
index 5c54deb..a3290f4 100644
--- a/public/pt_BR/index.html
+++ b/public/pt_BR/index.html
@@ -28,32 +28,32 @@
FAQ
ES6
- API Docs
+ Documentação da API
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
-
-Download for
-Linux,
-Win32, Win64,
-or
-Mac.
+Levando o ES6 para a Comunidade Node!
+io.js é uma plataforma compatível com o npm, originalmente baseada no node.js™.
+
+
+Download para
+Linux,
+Win32, Win64,
+ou
+Mac.
-Nightly releases are available for testing.
-
+Releases nightly estão disponíveis para testes.
+
diff --git a/public/pt_PT/es6.html b/public/pt_PT/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/pt_PT/es6.html
+++ b/public/pt_PT/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/pt_PT/index.html b/public/pt_PT/index.html
index 5c54deb..5d496a5 100644
--- a/public/pt_PT/index.html
+++ b/public/pt_PT/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/ru/es6.html b/public/ru/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/ru/es6.html
+++ b/public/ru/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/ru/index.html b/public/ru/index.html
index 5c54deb..5d496a5 100644
--- a/public/ru/index.html
+++ b/public/ru/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/sv/es6.html b/public/sv/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/sv/es6.html
+++ b/public/sv/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/sv/index.html b/public/sv/index.html
index 5c54deb..5d496a5 100644
--- a/public/sv/index.html
+++ b/public/sv/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/tr/es6.html b/public/tr/es6.html
index afdf1bd..0a9a6d0 100644
--- a/public/tr/es6.html
+++ b/public/tr/es6.html
@@ -34,7 +34,7 @@
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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@ Which ES6 features ship with io.js by default (no runtime flag required)?Set
-
+
+
+
+
diff --git a/public/tr/index.html b/public/tr/index.html
index 5c54deb..5d496a5 100644
--- a/public/tr/index.html
+++ b/public/tr/index.html
@@ -35,13 +35,13 @@
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
-
+
+
Download for
-Linux,
-Win32, Win64,
+Linux,
+Win32, Win64,
or
-Mac.
+Mac.
Nightly releases are available for testing.
diff --git a/public/zh_TW/es6.html b/public/zh_TW/es6.html
new file mode 100644
index 0000000..72e3343
--- /dev/null
+++ b/public/zh_TW/es6.html
@@ -0,0 +1,135 @@
+
+
+
+
+
+ io.js - JavaScript I/O
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ io.js 的 ES6
+io.js 建構於目前版本的 V8 之上，將會持續更新並引入最新的引擎版本，以確保最新的 JavaScript ECMA-262 specification 特性能以最短的時間內被 io.js 的開發人員所使用，並藉著不斷快速更新此持續改善效能及穩定度。
+目前釋出的 io.js v1.2.0 版本已採用 V8 4.1.0.14，其支援的 ES6 特性遠超過 joyent/node@0.12.x 所使用的 V8 3.26.23 。
+不再需要 --harmony 參數
+在 joyent/node@0.12.x (V8 3.26) 上，參數 --harmony 將會一次啟用所有處於完成（completed）、**階段性（staged）及程序中（in progress）**狀態之下的 ES6 特性支援（除了 proxies ，此特性在使用參數 --harmony-proxies 時會被隱藏）。這意味著一些臭蟲或是很有問題的特性像是 Arrow Functions ，可能將會很容易的被開發人員所誤用在專案中，就如同沒有問題的特性 generators 一般。因此，大多數的開發人員通常會代入一些參數，只啟動特定的 harmony 特性支援（如：--harmony-generators），或是直接啟用所有的特性支援，然後在開發時限定只使用特定某些穩定的功能。
+不過在使用 io.js@1.x (V8 4.1+) 之後，前面所提到的所有麻煩將不再是問題。現在所有的 harmony 特性都將會被分類到不同的群組中，分別為 shipping 、 staged 和 in progress：
+
+- 所有屬於 shipping 群組的特性，都是被 V8 認定為穩定（stable）的功能，如：generators 、 templates 、 new string methods 。值得一提的是，現在屬於此群組的更多特性都將被 預設啟用於 io.js ，且不需要在執行時添加使用任何參數。
+- 那些被歸類為 staged 群組的特性，都是功能上幾乎已經完整支援（almost-completed）的特性，但缺少測試或尚未支援到最新的 ES6 規格，所以尚未被 V8 的開發團隊視為穩定（stable）。這些特性的支援可能相當於 V8 3.26 時的 generators ，如果要使用，開發人員必須要自行承擔其風險，而且必須要在執行時使用
--es_staging 參數（同等於 --harmony）。
+- 最後，所有處於 in progress 群組的特性，可以以特定的參數啟用支援（如：
--harmony_arrow_functions，儘管這些特性不被推薦使用。
+
+什麼樣的 ES6 特性將被 io.js 預設支援？（不需要代入任何參數）
+
+-
+
Block scoping
+
+
+As of v8 3.31.74.1, block-scoped declarations are intentionally implemented with a non-compliant limitation to strict mode code. Developers should be aware that this will change as v8 continues towards ES6 specification compliance.
+
+
+-
+
Collections
+
+
+-
+
+
+-
+
+
+-
+
+
+-
+
+
+-
+
+
+-
+
+
+
+你可以參閱更多的細節，以及比較其他的 JavaScript 引擎，在 compat-table 專案網頁。
+什麼樣的 ES6 特性需要代入 --es_staging 參數？
+
+-
+
Classes 只有嚴格模式支援）
+
+-
+
+
+-
+
Symbol.toStringTag (user-definable results for Object.prototype.toString)
+
+
+我過去已經大量使用了 --harmony 參數，我該移除它嗎？
+目前 --harmony 在 io.js 的行為，只會啟用 staged 的特性，與 --es_staging 參數相同。如前面所提及，這些都是些尚未被視為穩定的特性，如果你想要更安全的使用 io.js ，尤其特別是在已上線的服務或產品上使用，請考慮移除並停止使用此參數，直到這些特性被 V8 所預設支援，接著被 io.js 所支援。假設你仍然持續使用這個參數，你可能要有因為升級 io.js 而導致程式壞掉的心理準備，尤其是如果 V8 為了更接近標準而修改語法，就會出現這樣的問題。
+我如何得知 io.js 正在使用的 V8 版本？
+io.js 提供了一個非常簡單的方法去取得所有的依賴函式庫及版本號，只要透過存取 process 全域物件即可。所以，如果想知道 V8 引擎的版本資訊，可以直接在終端機（Terminal）上輸入：
+iojs -p process.versions.v8
+
+
+
+
+
+
+
+
+
diff --git a/public/zh_TW/faq.html b/public/zh_TW/faq.html
new file mode 100644
index 0000000..1e2823f
--- /dev/null
+++ b/public/zh_TW/faq.html
@@ -0,0 +1,67 @@
+
+
+
+
+
+ io.js - JavaScript I/O
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 常見問題（FAQ）
+什麼是 io.js ？
+io.js 是一個以 Chrome's V8 runtime 為基礎的 JavaScript 應用程式開發平台，這個專案一開始是從 Joyent's Node.js™ 分支出來的一個版本，完全與 npm 相容。
+為什麼這麼做呢？
+io.js 目標將提供更快速且可預期的釋出週期，目前已經整合了最新的語言特性、API 以及 V8 的效能改進，此外也更新了 libuv 與其他的基礎函式庫。
+這個專案目標將以『開放管理模式（open governance model）』持續進行維護與開發，不同於被特定公司所主導發展的營運方式。
+版本 1.0.x？
+io.js 的改進與版本更新將遵守語意化版本控制規範（Semver），我們認為目前專案的發展狀況，完全有足夠的理由提升主版本號，使專案從 Node.js™ 0.10 到 io.js 1.0.0 版本。
+我們的 v1.x 版本的更新日誌將提供從 Node.js v0.10.35 到 io.js v1.0.x 版本的變更說明。
+我如何能貢獻？
+任何人都可以給予這個專案幫助，io.js 遵守行為準則（code of conduct）且接受不違反開放管理模式（open governance model）下的任何貢獻、釋出及貢獻關係。
+一開始，可以在discussions on GitHub進行公開討論，我們非常樂意聽到您的意見回饋。 加入並參與各種討論是一個找到能貢獻之處的好方法，如果你找到一個自己可以幫得上忙的事，請直接建立一個 pull request。
+此外，使用Nodebug.me 是一個協助社群指派分配任務的好方法。
+哪裡是一個進行討論的好地方？
+Freenode IRC 的 #io.js 頻道是一個可以進行討論的地方，我們將保存該頻道的討論紀錄在這。
+什麼是開放原始碼管理？
+開源管理方式引入開放原始碼的哲學以及開放內容運動，讓各個有興趣的團體對最終產品做出貢獻。其決策程序對於一般公民開放，就能夠以眾人的智慧來改善決策、深化參與。參考連結
+
+
+
+
+
+
+
+
diff --git a/public/zh_TW/index.html b/public/zh_TW/index.html
new file mode 100644
index 0000000..5de85f3
--- /dev/null
+++ b/public/zh_TW/index.html
@@ -0,0 +1,64 @@
+
+
+
+
+
+ io.js - JavaScript I/O
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/source/styles/main.styl b/source/styles/main.styl
index 3ac2e0a..402abad 100644
--- a/source/styles/main.styl
+++ b/source/styles/main.styl
@@ -8,6 +8,8 @@ html
line-height 1.5
-webkit-font-smoothing antialiased
-moz-osx-font-smoothing grayscale
+ -webkit-font-variant-ligatures none
+ font-variant-ligatures none
body
color #666
FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
-Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough -to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback. -Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is -something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+常见问题
+io.js 是什么？
+io.js 是基于 Chrome's V8 运行环境 的 JavaScript 平台。本项目是在原 Joyent's Node.js™ 项目基础上继续开发，且兼容 npm 生态系统。
+想知道原因？io.js 旨在提供更快和可预测的发布周期。目前它融合了最新的语言特性，API，V8 引擎的性能改进并且会持续更新 libuv 和其他底层库。
+本项目旨在让大家在 "开放的管理模式" 下持续开发和维护 io.js 从而避免受制于公司或小团体。
+1.0.x 版本？
+io.js 已经转移到 Semver 而且 io.js 1.0.0 相对于 Node.js™ 0.10 版本的改进和差异已经足够升一个 major。
+我们的 v1.x 发布日志 列出了 相对于 Node.js v0.10.35 版本的所有改进。
+如何贡献？
+每个人都可以提供帮助。io.js 的 代码合并，贡献，发布都会在 开放的管理模式 下完成。
+开始使用前不妨看一下我们在 GitHub 上的讨论，我们很乐意听到你的反馈. 亲身参与讨论会让你更加感同身受，以后更是可以提供更多帮助。如果你有想法参与贡献的话，敬请 提交 pull request。
+此外，最好通过 Nodebug.me 帮助分担积压的问题。
+哪里讨论？
+在 Freenode IRC 上有一个 #io.js 频道。历史记录在 这里。
+什么是开源管理？
+开源项目管理提倡共同维护开源且开放的内容，以便所有想贡献的人都可以参与进来，譬如一个wiki文档。开放的规则对每一位开发者都是公平的，集体的智慧更有利于决策项目和共建一个更加民主的氛围。[来自 wikipedia]
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, -or -Mac.
- -Nightly releases are available for testing.
- +为 Node 社区带来 ES6 ！
+io.js 是衍生于 node.js™ 并兼容 npm 的开发平台。
+
下载 +Linux, +Win32, Win64, +Mac, 或 其他 版本。
+ +每日构建版本 可用于测试。
+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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/da/es6.html b/public/da/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/da/es6.html +++ b/public/da/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/de/es6.html b/public/de/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/de/es6.html +++ b/public/de/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/el/es6.html b/public/el/es6.html index afdf1bd..88d977c 100644 --- a/public/el/es6.html +++ b/public/el/es6.html @@ -28,13 +28,13 @@ FAQ ES6 - API Docs + APIES6 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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
How do I find which version of V8 ships with a particular version of io.js?< diff --git a/public/el/faq.html b/public/el/faq.html index 6d92c81..df87a46 100644 --- a/public/el/faq.html +++ b/public/el/faq.html @@ -28,38 +28,37 @@ FAQ ES6 - API Docs + API
FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
-Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough -to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback. -Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is -something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+Τι σημαίνει io.js;
+io.js είναι μία JavaScript πλατφόρμα, βασισμένη στο V8 runtime του Chrome. Αυτό το πρότζεκτ ξεκίνησε σαν ένα fork του Node.js™ της Joyent, και είναι συμβατό με το οικοσύστημα του npm.
+Γιατί;
+Το io.js στοχεύει στο να παράσχει γρηγορότερες και πιο προβλέψιμες εκδόσεις. Αυτην την στιγμή, συγχωνεύει τις πιο πρόσφατες αλλαγές του V8 ως προς την γλώσσα, το API και τις βελτιώσεις στην απόδοση, ενώ παράλληλα προσφέρει αναβαθμίσεις από την βιβλιοθήκη libuv και άλλες βιβλιοθήκες.
+Το πρότζεκτ στοχεύει στην συνεχή ανάπτυξη του io.js, ύπο μία "ανοιχτή διακυβέρνηση" αντιθέτα από μία καθοδήγηση από κάποια εταιρία.
+Έκδοση 1.0.x;
+Το io.js πήγε σε Semver και οι αλλαγές μεταξύ Node.js™ 0.10 και io.js 1.0.0 είναι αρκετές για να υποστηρίξουν την αύξηση της κύριας έκδοσης (major version).
+Το ιστορικό αλλαγών για την v1.x παρέχει μία περίληψη των αλλαγών από το Node.js v0.10.35 στο io.js v1.0.x.
+Πως μπορώ να συνεισφέρω;
+Οποιοσδήποτε μπορεί να βοηθήσει. Το io.js υπακούει σε εναν κώδικα συμπεριφοράς, και οι συνεισφορές και εκδόσεις γίνονται με ένα μοντέλο "ανοιχτής διακυβέρνησης".
+Για να ξεκινήσετε, υπάρχουν ανοιχτές συζητήσεις στο GitHub, θα θέλαμε να ακούσουμε την γνώμη σας και τις απόψεις σας.
+Συμμετέχοντας στις συζητήσεις είναι ένας καλός τρόπος για να δείτε που και πως μπορείτε να βοηθήσετε το πρότζεκτ. Αν υπάρχει κάτι που θα θέλατε να προσθέσετε ή να βελτιώσετε, δημιουργήστε ένα pull request.
+Επίσης, χρησιμοποιώντας το Nodebug.me μπορείτε να λύσετε υπάρχοντα προβλήματα.
+Που γίνονται οι συζητήσεις;
+Υπάρχει ένα #io.js κανάλι στο Freenode IRC. Κρατάμε ιστορικό του καναλιού εδώ.
+Τι σημαίνει "ανοιχτή διακυβέρνηση";
+Η "ανοιχτή διακυβέρνηση" προωθεί τις αξίες του ανοιχτού κώδικα (open source) και του ανοιχτού περιεχομένου έτσι ώστε να μπορεί οποιοσδήποτε ενδιαφερόμενος να προσθέσει κάτι στην δημιουργία του τελικού αποτελέσματος, όπως σε ένα έγγραφο τύπου "wiki". Η νομοθεσία είναι δημοκρατικά ανοιχτή σε γενική κριτική έτσι ώστε να επωφεληθεί από τις γνώσεις όλων και να προωθεί την ιδέα της δημοκρατίας.
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, -or -Mac.
- -Nightly releases are available for testing.
- +Φέρνουμε την ES6 στην κοινότητα του Node!
+io.js είναι μια πλατφόρμα συμβατή με το npm, βασισμένη στο node.js™.
+
Κατεβάστε για +Linux, +Win32, +Win64, +Mac ή +others.
+ +Nightly εκδόσεις είναι διαθέσιμες για testing.
+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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.28.73 that ship with Node.js™ 0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.28.73 that ship with Node.js™ 0.12.x.
No more --harmony flag
On Node.js™@0.12.x (V8 3.28+), the --harmony runtime flag enables all completed, staged and in progress ES6 features together, in bulk (with the exception of proxies which are hidden under --harmony-proxies). This means that some really buggy or even broken features like Arrow Functions are just as readily available for developers as generators, which have very little or even no known-issues. As such, most developers tend to 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:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
Which ES6 features ship with io.js by default (no runtime flag required)?Which ES6 features are behind the --es_staging flag?
-
-
Classes (strict mode only)
+Classes (strict mode only, behind flag
--harmony_classeswhich implies block scoping & object literal extensions) -
-
+
Object literal extensions (behind flag
--harmony_object_literals) -
-
+Symbol.toStringTag(user-definable results forObject.prototype.toString)Symbol.toStringTag(user-definable results forObject.prototype.toString, behind flag--harmony_tostring)
Which ES6 features are in progress?
+New features are constantly being added to the V8 engine. Generally speaking, expect them to land on a future io.js release, although timing is unknown.
+You may list all the in progress features available on each io.js release by grepping through the --v8-options argument. Please note that these are incomplete and possibly broken features of V8, so use them at your own risk:
iojs --v8-options | grep "in progress"
+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?
diff --git a/public/en/index.html b/public/en/index.html index 3c2dfd2..e92c495 100644 --- a/public/en/index.html +++ b/public/en/index.html @@ -35,14 +35,14 @@JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, -Win64, -Mac or -others.
+Linux, +Win32, +Win64, +Mac or +others.Nightly releases are available for testing.
diff --git a/public/es/es6.html b/public/es/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/es/es6.html +++ b/public/es/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/es_AR/es6.html b/public/es_AR/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/es_AR/es6.html +++ b/public/es_AR/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/es_CO/es6.html b/public/es_CO/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/es_CO/es6.html +++ b/public/es_CO/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/es_ES/es6.html b/public/es_ES/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/es_ES/es6.html +++ b/public/es_ES/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/fr/es6.html b/public/fr/es6.html index afdf1bd..e0137e6 100644 --- a/public/fr/es6.html +++ b/public/fr/es6.html @@ -28,13 +28,13 @@ FAQ ES6 - API Docs + Doc de l'APIES6 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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
How do I find which version of V8 ships with a particular version of io.js?< diff --git a/public/fr/faq.html b/public/fr/faq.html index 6d92c81..6d8977c 100644 --- a/public/fr/faq.html +++ b/public/fr/faq.html @@ -28,38 +28,37 @@ FAQ ES6 - API Docs + Doc de l'API
FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
+Qu'est-ce que io.js?
+io.js est une plateforme JavaScript construite sur le moteur d'exécution de Chrome's, V8. Ce projet a commencé comme un fork de Node.js™ de Joyent et est compatible avec l'écosystème npm.
+Pourquoi? L'objectif de io.js est de fournir des cycles de développement plus rapides et prévisibles. Il fusionne actuellement les dernières fonctionnalités du langage, API et améliorations de performance de V8 tout en mettant à jour libuv et d'autres bibliothèques de base.
+Ce projet vise à poursuivre le développement de io.js sous un "modèle de gouvernance ouvert" par opposition à la gérance de Node.js™ organisée par Joyent, jugée restreinte.
Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough -to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback. -Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is -something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+io.js est passé à une gestion sémantique de version, Semver et les changements entre Node.js™ 0.10 et io.js 1.0.0 sont assez significatifs pour légitimer le passage à une nouvelle version majeure.
+Notre CHANGELOG pour la v1.x fournit un résumé des changements effectués entre Node.js v0.10.35 et io.js v1.0.x.
+Comment puis-je contribuer?
+Tout le monde peut aider. Io.js adhère à un code de conduite, et les contributions sont sous un modèle de gouvernance ouverte.
+Pour commencer, il y a des discussions ouvertes sur GitHub, et nous aimerons entendre votre avis. +S'impliquer dans les discussions est un bon moyen pour savoir comment aider davantage. S'il y a +quelque chose que vous vous sentez capable d'améliorer, créez une pull request.
+En outre, utiliser Nodebug.me est un bon moyen pour aider au triage des issues dans le backlog.
+Où les discussions ont-elles lieu?
+Il y a un canal de discussion IRC #io.js sur Freenode. Nous gardons les logs du canal ici.
+Qu'est-ce que la gouvernance open source?
+La gouvernance open source préconise l'application de la philosophie des mouvements open source et open content dans afin de permettre toute personne intéressée de contribuer à la création finale du produit, comme dans un document wiki. La législation est démocratiquement ouverte à l'ensemble des citoyens, employant leur sagesse collective afin d'en faire bénéficier le processus de décision et améliorer la démocratie. [source]
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, -or -Mac.
+ES6 pour la communauté Node!
+io.js est une plateforme compatible avec npm et basée sur node.js™.
+
Télécharger pour +Linux, +Win32, Win64, +ou +Mac.
-Nightly releases are available for testing.
- +Les Nightly releases sont disponibles pour des tests.
+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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/hi/es6.html b/public/hi/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/hi/es6.html +++ b/public/hi/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/hu/es6.html b/public/hu/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/hu/es6.html +++ b/public/hu/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/id/es6.html b/public/id/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/id/es6.html +++ b/public/id/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/it/es6.html b/public/it/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/it/es6.html +++ b/public/it/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/jp/es6.html b/public/jp/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/jp/es6.html +++ b/public/jp/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/ka/es6.html b/public/ka/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/ka/es6.html +++ b/public/ka/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/kr/es6.html b/public/kr/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/kr/es6.html +++ b/public/kr/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/mk/es6.html b/public/mk/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/mk/es6.html +++ b/public/mk/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/nl/es6.html b/public/nl/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/nl/es6.html +++ b/public/nl/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/no/es6.html b/public/no/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/no/es6.html +++ b/public/no/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/pl/es6.html b/public/pl/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/pl/es6.html +++ b/public/pl/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/pt_BR/es6.html b/public/pt_BR/es6.html index afdf1bd..4e28eb6 100644 --- a/public/pt_BR/es6.html +++ b/public/pt_BR/es6.html @@ -28,25 +28,25 @@ FAQ ES6 - API Docs + Documentação da APIES6 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.1.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
+ES6 no io.js
+O io.js é construído usando versões modernas do V8. Mantendo-nos atualizados com as últimas versões desta engine, garantimos que novas funcionalidades da especificação JavaScript ECMA-262 são trazidas para desenvolvedores io.js rapidamente, além de manter performance continuada e melhorias de estabilidade.
+A versão 1.2.0 do io.js vem com o V8 4.1.0.14, que inclui funcionalidades do ES6 bem além da versão 3.26.33 que vem com o joyent/node@0.12.x.
+Não mais flag --harmony
+No joyent/node@0.12.x (V8 3.26), a flag de runtime --harmony habilitava todas funcionalidades ES6 completas, em teste e em progresso juntas, de uma vez só (com a exceção de semânticas não padrão/não harmoniosas para typeof que estavam escondidas sob --harmony-typeof). Isto significava que algumas funcionalidades realmente bugadas ou mesmo quebradas como os proxies estavam prontamente disponíveis para desenvolvedores como os generators, que tinham poucos ou mesmo nenhuma issue conhecida. Portanto, era uma boa prática ou habilitar apenas certas funcionalidades usando flags de runtime harmony para funcionalidades específicas (por ex. --harmony-generators), ou simplesmente habilitar tudo e depois usar apenas um subconjunto restrito.
Com o io.js@1.x (V8 4.1+), toda esta complexidade vai embora. Todas as funcionalidades harmony agora estão logicamente divididas em três grupos para funcionalidades entregues, sob testes e em progresso:
-
-
- 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.
+ - Todas funcionalidades entregues, aquelas consideradas estáveis pelo V8, como generators, templates, novos métodos de string e muitas outras são habilitadas por padrão no io.js e NÃO requerem qualquer tipo de flag de runtime. +
- Então há as funcionalidades em testes que são funcionalidades quase completas que não foram completamente testadas ou atualizadas com a última especificação e portanto não são consideradas estáveis pela equipe do V8 (por ex. pode haver alguns edge cases restando a descobrir). Isto é provavelmente o equivalente ao estado dos generators no 3.26. Estas são funcionalidades do tipo "use sob seu próprio risco" que agora requerem a flag:
--es_staging(ou seu sinônimo,--harmony).
+ - Finalmente, todas funcionalidades em progresso podem ser ativadas individualmente pela sua respectiva flag harmony (por ex.
--harmony_arrow_functions). No entanto, isto é altamente desemcorajado a não ser para fins de teste.
Which ES6 features ship with io.js by default (no runtime flag required)?
+Que funcionalidades ES6 estão disponíveis por padrão no io.js (sem requerer flag)?
-
-
Block scoping
+Escopo de bloco
-
@@ -55,15 +55,15 @@
Which ES6 features ship with io.js by default (no runtime flag required)?const
-
-
+function-in-blocksfunctionem blocos
-
As of v8 3.31.74.1, block-scoped declarations are intentionally implemented with a non-compliant limitation to strict mode code. Developers should be aware that this will change as v8 continues towards ES6 specification compliance.
+Desde o v8 3.31.74.1, declarações em escopo de bloco são intencionalmente implementadas como uma limitação em não conformidade com código em modo estrito. Desenvolvedores devem estar cientes que isto deve mudar assim que o v8 continuar em direção à conformidade com a especificação ES6.
-
@@ -55,15 +55,15 @@
-
-
Collections
+Coleções
-
@@ -75,54 +75,57 @@
Which ES6 features ship with io.js by default (no runtime flag required)?Set
- - +
-
@@ -75,54 +75,57 @@
- - + + +
- +
- - +
- - +
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?
+Você pode ver uma lista mais detalhada, incluindo uma comparação com outras engines, no página do projeto da tabela de compatibilidade.
+Que funcionalidades ES6 estão sob a flag --es_staging?
-
-
Classes (strict mode only)
+Classes (modo estrito apenas)
- - +
-
-
+Symbol.toStringTag(user-definable results forObject.prototype.toString)Symbol.toStringTag(resultados definidos pelo usuário paraObject.prototype.toString)
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:
Eu tenho minha própria infraestrutura configurada para usar a flag --harmony. Devo removê-la?
+O comportamento atual da flag --harmony no io.js é para habilitar funcionalidades em testes apenas. Além disso, ela é agora um sinônimo de --es_staging. Como mencionado acima, estas são funcionalidades completas que não foram consideradas estáveis ainda. Se você quiser manter-se seguro, especialmente em ambientes de produção, considere remover esta flag de runtime até que ela seja disponibilizada por padrão no V8 e, consequentemente, no io.js. Se você mantê-la habilitada, você deve estar preparado para que futuras atualizações do io.js quebrem seu código se o V8 alterar suas semânticas para ter uma maior conformidade com a especificação.
Como posso saber que versão do V8 está disponível com uma versão específica do io.js?
+O io.js fornece uma maneira simples de listar todas as dependências e suas respectivas versões que são disponibilizadas em um binário através do objeto global process. No caso da engine V8, digite o seguinte em seu terminal para obter sua versão:
iojs -p process.versions.v8
FAQ
-What is io.js?
-io.js is a JavaScript platform built on Chrome's V8 runtime. This project began as a fork of Joyent's Node.js™ and is compatible with the npm ecosystem.
-Why? io.js aims to provide faster and predictable release cycles. It currently merges in the latest language, API and performance improvements to V8 while also updating libuv and other base libraries.
-This project aims to continue development of io.js under an "open governance model" as opposed to corporate stewardship.
-Version 1.0.x?
-io.js has moved to Semver and the changes between Node.js™ 0.10 and io.js 1.0.0 were significant enough -to warrant a major version increment.
-Our CHANGELOG for v1.x provides a summary of changes from Node.js v0.10.35 to io.js v1.0.x.
-How can I contribute?
-Everyone can help. io.js adheres to a code of conduct, and contributions, releases, and contributorship are under an open governance model.
-To get started, there are open discussions on GitHub, and we'd love to hear your feedback. -Becoming involved in discussions is a good way to get a feel of where you can help out further. If there is -something there you feel you can tackle, please make a pull request.
-In addition, using Nodebug.me is a good way to help Triage the issues in the backlog.
-Where do discussions take place?
-There is an #io.js channel on Freenode IRC. We keep logs of the channel here.
-What is open source governance?
-Open source governance advocates the application of the philosophies of the open source and open content movements in order to enable any interested party to add to the creation of the end product, as with a wiki document. Legislation is democratically opened to the general citizenry, employing their collective wisdom to benefit the decision-making process and improve democracy. [source]
+O que é io.js?
+io.js é uma plataforma JavaScript construída no Chrome's V8 runtime. Esse projeto começou como um fork do Node.js™ da Joyent e é compátivel com o ecossistema npm.
+Por que? O io.js visa fornecer ciclos de release mais rápidos e previsíveis. Atualmente ele traz as últimas melhorias em linguagem, API e desempenho do V8 e ao mesmo tempo atualizando a libuv e outras bibliotecas base.
+Este projeto tem como objetivo continuar o desenvolvimento do io.js sob um "modelo de governança aberto" em oposição à administração corporativa.
+Versão 1.0.x?
+io.js passou a usar Semver e as mudanças entre o Node.js™ 0.10 e io.js 1.0.0 foram significativas o suficiente para justificar um grande incremento da versão.
+Nosso CHANGELOG para a v1.x fornece um resumo das alterações do Node.js v0.10.35 para o io.js v1.0.x.
+Como posso contribuir?
+Todos podem ajudar. O io.js adere a um código de conduta, e contribuições, lançamentos e autoria de contribuições estão sob um modelo de governaça aberta.
+Para começar, abra uma issue no GitHub, e nós vamos adorar ouvir seu feedback. +Envolver-se em discussões é uma boa forma de ter uma sensação de que você pode ajudar ainda mais. Se houver algo que você sente que você pode resolver, por favor faça um pull request.
+Além disso, usar o Nodebug.me é uma boa forma de ajudar na triagem de issues no backlog.
+Onde as discussões acontecem?
+Há um canal #io.js no IRC Freenode. Nós mantemos os logs do canal aqui.
+O que é governança de código aberto?
+A governança de código aberto defende a aplicação das filosofias do Open Source e dos movimentos de conteúdo aberto, a fim de permitir que todos os interessados possam acrescentar à criação do produto final, como acontece com um documento Wiki. A legislação é democraticamente aberta aos cidadãos em geral, empregando sua sabedoria coletiva para beneficiar o processo de tomada de decisão e melhorar a democracia. [fonte]
JavaScript I/O
-Bringing ES6 to the Node Community!
-io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, -or -Mac.
+Levando o ES6 para a Comunidade Node!
+io.js é uma plataforma compatível com o npm, originalmente baseada no node.js™.
+
Download para +Linux, +Win32, Win64, +ou +Mac.
-Nightly releases are available for testing.
- +Releases nightly estão disponíveis para testes.
+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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/ru/es6.html b/public/ru/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/ru/es6.html +++ b/public/ru/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/sv/es6.html b/public/sv/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/sv/es6.html +++ b/public/sv/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/tr/es6.html b/public/tr/es6.html index afdf1bd..0a9a6d0 100644 --- a/public/tr/es6.html +++ b/public/tr/es6.html @@ -34,7 +34,7 @@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.1.0 of io.js ships with V8 4.1.0.14, which includes ES6 features well beyond version 3.26.33 that will be shipped with joyent/node@0.12.x.
+Version 1.2.0 of io.js ships with V8 4.1.0.14, 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 4.1+), all that complexity goes away. All harmony features are now logically split into three groups for shipping, staged and in progress features:
@@ -75,11 +75,14 @@Which ES6 features ship with io.js by default (no runtime flag required)?Set
JavaScript I/O
Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.
-
Download for -Linux, -Win32, Win64, +Linux, +Win32, Win64, or -Mac.
+Mac.Nightly releases are available for testing.
diff --git a/public/zh_TW/es6.html b/public/zh_TW/es6.html new file mode 100644 index 0000000..72e3343 --- /dev/null +++ b/public/zh_TW/es6.html @@ -0,0 +1,135 @@ + + + + + +io.js 的 ES6
+io.js 建構於目前版本的 V8 之上，將會持續更新並引入最新的引擎版本，以確保最新的 JavaScript ECMA-262 specification 特性能以最短的時間內被 io.js 的開發人員所使用，並藉著不斷快速更新此持續改善效能及穩定度。
+目前釋出的 io.js v1.2.0 版本已採用 V8 4.1.0.14，其支援的 ES6 特性遠超過 joyent/node@0.12.x 所使用的 V8 3.26.23 。
+不再需要 --harmony 參數
+在 joyent/node@0.12.x (V8 3.26) 上，參數 --harmony 將會一次啟用所有處於完成（completed）、**階段性（staged）及程序中（in progress）**狀態之下的 ES6 特性支援（除了 proxies ，此特性在使用參數 --harmony-proxies 時會被隱藏）。這意味著一些臭蟲或是很有問題的特性像是 Arrow Functions ，可能將會很容易的被開發人員所誤用在專案中，就如同沒有問題的特性 generators 一般。因此，大多數的開發人員通常會代入一些參數，只啟動特定的 harmony 特性支援（如：--harmony-generators），或是直接啟用所有的特性支援，然後在開發時限定只使用特定某些穩定的功能。
不過在使用 io.js@1.x (V8 4.1+) 之後，前面所提到的所有麻煩將不再是問題。現在所有的 harmony 特性都將會被分類到不同的群組中，分別為 shipping 、 staged 和 in progress：
+-
+
- 所有屬於 shipping 群組的特性，都是被 V8 認定為穩定（stable）的功能，如：generators 、 templates 、 new string methods 。值得一提的是，現在屬於此群組的更多特性都將被 預設啟用於 io.js ，且不需要在執行時添加使用任何參數。 +
- 那些被歸類為 staged 群組的特性，都是功能上幾乎已經完整支援（almost-completed）的特性，但缺少測試或尚未支援到最新的 ES6 規格，所以尚未被 V8 的開發團隊視為穩定（stable）。這些特性的支援可能相當於 V8 3.26 時的 generators ，如果要使用，開發人員必須要自行承擔其風險，而且必須要在執行時使用
--es_staging參數（同等於--harmony）。
+ - 最後，所有處於 in progress 群組的特性，可以以特定的參數啟用支援（如：
--harmony_arrow_functions，儘管這些特性不被推薦使用。
+
什麼樣的 ES6 特性將被 io.js 預設支援？（不需要代入任何參數）
+-
+
-
+
Block scoping
+ ++
+As of v8 3.31.74.1, block-scoped declarations are intentionally implemented with a non-compliant limitation to strict mode code. Developers should be aware that this will change as v8 continues towards ES6 specification compliance.
+
+ -
+
Collections
+ +
+ - + + +
- + + +
- + + +
- + + +
- + + +
- + + +
你可以參閱更多的細節，以及比較其他的 JavaScript 引擎，在 compat-table 專案網頁。
+什麼樣的 ES6 特性需要代入 --es_staging 參數？
+-
+
-
+
Classes 只有嚴格模式支援）
+
+ - + + +
-
+
+Symbol.toStringTag(user-definable results forObject.prototype.toString)
+
我過去已經大量使用了 --harmony 參數，我該移除它嗎？
+目前 --harmony 在 io.js 的行為，只會啟用 staged 的特性，與 --es_staging 參數相同。如前面所提及，這些都是些尚未被視為穩定的特性，如果你想要更安全的使用 io.js ，尤其特別是在已上線的服務或產品上使用，請考慮移除並停止使用此參數，直到這些特性被 V8 所預設支援，接著被 io.js 所支援。假設你仍然持續使用這個參數，你可能要有因為升級 io.js 而導致程式壞掉的心理準備，尤其是如果 V8 為了更接近標準而修改語法，就會出現這樣的問題。
我如何得知 io.js 正在使用的 V8 版本？
+io.js 提供了一個非常簡單的方法去取得所有的依賴函式庫及版本號，只要透過存取 process 全域物件即可。所以，如果想知道 V8 引擎的版本資訊，可以直接在終端機（Terminal）上輸入：
iojs -p process.versions.v8
+常見問題（FAQ）
+什麼是 io.js ？
+io.js 是一個以 Chrome's V8 runtime 為基礎的 JavaScript 應用程式開發平台，這個專案一開始是從 Joyent's Node.js™ 分支出來的一個版本，完全與 npm 相容。
+為什麼這麼做呢？
+io.js 目標將提供更快速且可預期的釋出週期，目前已經整合了最新的語言特性、API 以及 V8 的效能改進，此外也更新了 libuv 與其他的基礎函式庫。
+這個專案目標將以『開放管理模式（open governance model）』持續進行維護與開發，不同於被特定公司所主導發展的營運方式。
+版本 1.0.x？
+io.js 的改進與版本更新將遵守語意化版本控制規範（Semver），我們認為目前專案的發展狀況，完全有足夠的理由提升主版本號，使專案從 Node.js™ 0.10 到 io.js 1.0.0 版本。
+我們的 v1.x 版本的更新日誌將提供從 Node.js v0.10.35 到 io.js v1.0.x 版本的變更說明。
+我如何能貢獻？
+任何人都可以給予這個專案幫助，io.js 遵守行為準則（code of conduct）且接受不違反開放管理模式（open governance model）下的任何貢獻、釋出及貢獻關係。
+一開始，可以在discussions on GitHub進行公開討論，我們非常樂意聽到您的意見回饋。 加入並參與各種討論是一個找到能貢獻之處的好方法，如果你找到一個自己可以幫得上忙的事，請直接建立一個 pull request。
+此外，使用Nodebug.me 是一個協助社群指派分配任務的好方法。
+哪裡是一個進行討論的好地方？
+Freenode IRC 的 #io.js 頻道是一個可以進行討論的地方，我們將保存該頻道的討論紀錄在這。
+什麼是開放原始碼管理？
+開源管理方式引入開放原始碼的哲學以及開放內容運動，讓各個有興趣的團體對最終產品做出貢獻。其決策程序對於一般公民開放，就能夠以眾人的智慧來改善決策、深化參與。參考連結
+