Weekly io.js, February 13, 2015
Localization in 29 languages, release 1.2.0, and much more.
On February 13th, io.js made it to the 10,000 star mark on GitHub. We could not have achieved this without the support of the JS community. Thanks you!
You can see the original article here .
You can read the original article here .
We cannot wait to forget about the split with node.js, but we cannot sacrifice the progress, principles, and the management model that we have implemented.
For the community, nothing is changing.
This is a translation of the article io.js Week of February 13th 2015, which you can find on medium .
Added support for io.js ...
Io.js repository on GitHub scores 10,000 stars
On February 13th, io.js made it to the 10,000 star mark on GitHub. We could not have achieved this without the support of the JS community. Thanks you!
Io.js version 1.2.0 released
- stream : simplified creation.
- dns : the argument “all” was added to lookup (), which defaults to false, but if set to true, lookup will return an array of all ip addresses for the specified hostname.
- assert : removed the comparison of the prototype property in deepEqual () and added the deepStrictEqual () method, which repeats deepEqual () , but does a strict comparison of primitives.
- tracing : added support for LTTng (Linux Trace Toolkit Next Generation) when compiling with the “–with-lttng” option. Trace points repeat available from DTrace and ETW.
- docs : Many changes to the documentation, see individual commits; new page describing the specifics of JavaScript, V8 and io.js. errors
- npm updated to version 2.5.1
- libuv has been updated to version 1.4.0, you can read the full list of changes here .
- The team io.js added: Aleksey Smolenchuk ( LXE ) and Ohtsu Shigeki ( Shigeki )
We opened the door to the world community
You can see the original article here .
- Interested participants were added to the teams of different languages.
- Teams have registered accounts on Twitter and other social networks.
- Each team has come up with its own work process and has become not just translators, but community organizers.
Localization Statistics
- on the first day, 146 participants expressed a desire to help in localization (now their number is more than 160)
- 27 language groups were created on the first day (now there are 29)
Repository Links
- iojs-bn bengali
- iojs-cn chinese
- iojs-cs czech
- iojs-da Danish
- iojs-de german
- iojs-el greek
- iojs-es spanish
- iojs-fa persian
- iojs-fi finnish
- iojs-fr french
- iojs-he Hebrew
- iojs-hi hindi
- iojs-hu hungarian
- iojs-id Indonesian
- iojs-it italian
- iojs-ja japanese
- iojs-ka georgian
- iojs-kr korean
- iojs-mk macedonian
- iojs-nl Dutch
- iojs-no norwegian
- iojs-pl polish
- iojs-pt portuguese
- iojs-ro romanian
- iojs-ru russian
- iojs-sv swedish
- iojs-tr Turkish
- iojs-tw Taiwan
- iojs-uk Ukrainian
io.js and node.js
You can read the original article here .
- Scott Hammond, CEO of Joyent, has expressed a desire to bring io.js back to node.js.
In just a few months, the io.js project ...
- Grew up to 23 active members of the main team
- Multi working groups
- 29 localization teams,
- Attracted more participants than node.js since its inception.
- With the support of the community, it produces quality software.
We cannot wait to forget about the split with node.js, but we cannot sacrifice the progress, principles, and the management model that we have implemented.
Future
- Negotiations are underway with node.js.
- As soon as the optimal control model is selected, a discussion on GitHub will begin on whether io.js is worth joining node.js. Voting on this issue will take place at a public meeting of the technical committee.
For the community, nothing is changing.
What can you do now
- Continue to send pull requests
- Add to one of 27 localization commands
- Help one of the working groups ( streams , website , evangelism , tracing , build , roadmap ) and
- Continue to use io.js in your projects.
This is a translation of the article io.js Week of February 13th 2015, which you can find on medium .