diff --git a/content/cs/es6.md b/content/cs/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/cs/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/cs/faq.md b/content/cs/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/cs/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/cs/index.md b/content/cs/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/cs/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/da/es6.md b/content/da/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/da/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/da/faq.md b/content/da/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/da/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/da/index.md b/content/da/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/da/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/de/es6.md b/content/de/es6.md index 3f1ee6c..75a0d2f 100644 --- a/content/de/es6.md +++ b/content/de/es6.md @@ -1,71 +1,5 @@ -# ES6 on io.js + + + -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` + diff --git a/content/hi/es6.md b/content/hi/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/hi/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/hi/faq.md b/content/hi/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/hi/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/hi/index.md b/content/hi/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/hi/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/hu/es6.md b/content/hu/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/hu/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/hu/faq.md b/content/hu/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/hu/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/hu/index.md b/content/hu/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/hu/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/ka/es6.md b/content/ka/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/ka/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/ka/faq.md b/content/ka/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/ka/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/ka/index.md b/content/ka/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/ka/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/mk/es6.md b/content/mk/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/mk/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/mk/faq.md b/content/mk/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/mk/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/mk/index.md b/content/mk/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/mk/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/nl/es6.md b/content/nl/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/nl/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/nl/faq.md b/content/nl/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/nl/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/nl/index.md b/content/nl/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/nl/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/pl/es6.md b/content/pl/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/pl/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/pl/faq.md b/content/pl/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/pl/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/pl/index.md b/content/pl/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/pl/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/content/sv/es6.md b/content/sv/es6.md deleted file mode 100644 index 3f1ee6c..0000000 --- a/content/sv/es6.md +++ /dev/null @@ -1,71 +0,0 @@ -# ES6 on io.js - -io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements. - -Version {{project.current_version}} of io.js ships with V8 {{project.current_v8}}, 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), 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: - -* All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) 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](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`). -* Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes. - -## Which ES6 features ship with io.js by default (no runtime flag required)? - - -* Block scoping - - * [let](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let) - - * [const](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const) - - * `function`-in-blocks - - >As of v8 3.31.74.1, block-scoped declarations are [intentionally implemented with a non-compliant limitation to strict mode code](https://groups.google.com/forum/#!topic/v8-users/3UXNCkAU8Es). Developers should be aware that this will change as v8 continues towards ES6 specification compliance. - -* Collections - - * [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) - - * [WeakMap](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap) - - * [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) - - * [WeakSet](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakSet) - -* [Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) - -* [Binary and Octal literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Numeric_literals) - -* [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) - -* [New String methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) - -* [Symbols](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) - -* [Template strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings) - -You can view a more detailed list, including a comparison with other engines, on the [compat-table](https://kangax.github.io/compat-table/es6/) project page. - -## Which ES6 features are behind the --es_staging flag? - -* [Classes](https://github.com/lukehoban/es6features#classes) (strict mode only) -* [Object literal extensions](https://github.com/lukehoban/es6features#enhanced-object-literals) - -* [`Symbol.toStringTag`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol) (user-definable results for `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: - -```sh -iojs -p process.versions.v8 -``` diff --git a/content/sv/faq.md b/content/sv/faq.md deleted file mode 100644 index bd0c0f4..0000000 --- a/content/sv/faq.md +++ /dev/null @@ -1,34 +0,0 @@ -# FAQ - -## What is io.js? - -[io.js](https://github.com/iojs/io.js) is a JavaScript platform built on [Chrome's V8 runtime](http://code.google.com/p/v8/). This project began as a fork of [Joyent's Node.js™](https://nodejs.org/) and is compatible with the [npm](https://www.npmjs.org/) 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](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme)" as opposed to corporate stewardship. - -## Version 1.0.x? - -io.js has moved to [Semver](http://semver.org/) 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](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) for v1.x provides a [summary of changes from Node.js v0.10.35 to io.js v1.0.x](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#summary-of-changes-from-nodejs-v01035-to-iojs-v100). - -## How can I contribute? - -Everyone can help. io.js adheres to a [code of conduct](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-of-conduct), and contributions, releases, and contributorship are under an [open governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme) model. - -To get started, there are open [ discussions on GitHub](https://github.com/iojs/io.js/issues), 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](https://github.com/iojs/io.js/blob/v1.x/CONTRIBUTING.md#code-contributions). - -In addition, using [Nodebug.me](http://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](http://logs.libuv.org/io.js/latest). - -## 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]](https://en.wikipedia.org/wiki/Open-source_governance) \ No newline at end of file diff --git a/content/sv/index.md b/content/sv/index.md deleted file mode 100644 index aba9f2c..0000000 --- a/content/sv/index.md +++ /dev/null @@ -1,22 +0,0 @@ -# JavaScript I/O - -Bringing [ES6](es6.html) to the Node Community! - -[io.js](https://github.com/iojs/io.js) is an [npm](https://www.npmjs.org/) compatible platform originally based on [node.js](https://nodejs.org/)™. - -[![io.js](../images/1.0.0.png)](https://iojs.org/dist/v{{project.current_version}}/) - -[Version {{project.current_version}}](https://iojs.org/dist/v{{project.current_version}}/) - -Download for -[Linux](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-linux-x64.tar.xz), -[Win32](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x86.msi), [Win64](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}-x64.msi), -or -[Mac](https://iojs.org/dist/v{{project.current_version}}/iojs-v{{project.current_version}}.pkg). - - -[Changelog](https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md) - -[Nightly releases](https://iojs.org/download/nightly/) are available for testing. - -[Frequently Asked Questions](/faq.html) diff --git a/public/cs/es6.html b/public/cs/es6.html deleted file mode 100644 index b8cc495..0000000 --- a/public/cs/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/cs/faq.html b/public/cs/faq.html deleted file mode 100644 index 6f6ad71..0000000 --- a/public/cs/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/cs/index.html b/public/cs/index.html deleted file mode 100644 index 9c8c0e8..0000000 --- a/public/cs/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/da/es6.html b/public/da/es6.html deleted file mode 100644 index a5d79d2..0000000 --- a/public/da/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/da/faq.html b/public/da/faq.html deleted file mode 100644 index 749ea38..0000000 --- a/public/da/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/da/index.html b/public/da/index.html deleted file mode 100644 index 88af63c..0000000 --- a/public/da/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/hi/es6.html b/public/hi/es6.html deleted file mode 100644 index 5c84fe3..0000000 --- a/public/hi/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/hi/faq.html b/public/hi/faq.html deleted file mode 100644 index 7b17c20..0000000 --- a/public/hi/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/hi/index.html b/public/hi/index.html deleted file mode 100644 index 3f394b5..0000000 --- a/public/hi/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/hu/es6.html b/public/hu/es6.html deleted file mode 100644 index 4f7b1ae..0000000 --- a/public/hu/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/hu/faq.html b/public/hu/faq.html deleted file mode 100644 index 755e476..0000000 --- a/public/hu/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/hu/index.html b/public/hu/index.html deleted file mode 100644 index 717d668..0000000 --- a/public/hu/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/ka/es6.html b/public/ka/es6.html deleted file mode 100644 index b254b28..0000000 --- a/public/ka/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/ka/faq.html b/public/ka/faq.html deleted file mode 100644 index 22622c7..0000000 --- a/public/ka/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/ka/index.html b/public/ka/index.html deleted file mode 100644 index 479d3f4..0000000 --- a/public/ka/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/mk/es6.html b/public/mk/es6.html deleted file mode 100644 index 5d5b1e0..0000000 --- a/public/mk/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/mk/faq.html b/public/mk/faq.html deleted file mode 100644 index 18f065f..0000000 --- a/public/mk/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/mk/index.html b/public/mk/index.html deleted file mode 100644 index 81ca27d..0000000 --- a/public/mk/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/nl/es6.html b/public/nl/es6.html deleted file mode 100644 index 957a096..0000000 --- a/public/nl/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/nl/faq.html b/public/nl/faq.html deleted file mode 100644 index 24d1de1..0000000 --- a/public/nl/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/nl/index.html b/public/nl/index.html deleted file mode 100644 index 96c7e6c..0000000 --- a/public/nl/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/pl/es6.html b/public/pl/es6.html deleted file mode 100644 index cc27314..0000000 --- a/public/pl/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/pl/faq.html b/public/pl/faq.html deleted file mode 100644 index 67fbac7..0000000 --- a/public/pl/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/pl/index.html b/public/pl/index.html deleted file mode 100644 index 194ca6e..0000000 --- a/public/pl/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - - diff --git a/public/sv/es6.html b/public/sv/es6.html deleted file mode 100644 index 82d7ff7..0000000 --- a/public/sv/es6.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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.4.3 of io.js ships with V8 4.1.0.21, 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:

- -

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

- -

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

-

Which ES6 features are behind the --es_staging flag?

- -

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

-

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

-

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

-

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

-
iojs -p process.versions.v8
-
-
- - - - - - - - diff --git a/public/sv/faq.html b/public/sv/faq.html deleted file mode 100644 index 3f361e0..0000000 --- a/public/sv/faq.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

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]

-
- - - - - - - - diff --git a/public/sv/index.html b/public/sv/index.html deleted file mode 100644 index 9c4a323..0000000 --- a/public/sv/index.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - io.js - JavaScript I/O - - - - - - - - - - - - - - - - - - -
-
- -
- FAQ - ES6 - API Docs -
-
- -

JavaScript I/O

-

Bringing ES6 to the Node Community!

-

io.js is an npm compatible platform originally based on node.js™.

-

io.js

-

Version 1.4.3

-

Download for -Linux, -Win32, Win64, -or -Mac.

-

Changelog

-

Nightly releases are available for testing.

-

Frequently Asked Questions

-
- - - - - - - -