Evangelism: Weekly Update Feb 27th

[bnb]

io.js 1.4.1 Release

Note: version 1.4.0 was tagged and built but not released. A libuv bug was discovered in the process so the release was aborted. We have jumped to 1.4.1 to avoid confusion.

Notable changes

• process / promises: An'unhandledRejection' event is now emitted on process whenever a Promise is rejected and no error handler is attached to the Promise within a turn of the event loop. A 'rejectionHandled' event is now emitted whenever a Promise was rejected and an error handler was attached to it later than after an event loop turn. #758 (Petka Antonov)
• streams: you can now use regular streams as an underlying socket for tls.connect() #926 (Fedor Indutny)
• http: A new 'abort' event emitted when a http.ClientRequest is aborted by the client. #945 (Evan Lucas)
• V8: Upgrade V8 to 4.1.0.21. Includes an embargoed fix, details should be available when embargo is lifted. A breaking ABI change has been held back from this upgrade, possibly to be included when io.js merges V8 4.2. See #952 for discussion.
• npm: Upgrade npm to 2.6.0. Includes features to support the new registry and to prepare for npm@3. See npm CHANGELOG.md for details. Summary:
  • #5068 Add new logout command, and make it do something useful on both bearer-based and basic-based authed clients.
  • #6565 Warn that peerDependency behavior is changing and add a note to the docs.
  • #7171 Warn that engineStrict in package.json will be going away in the next major version of npm (coming soon!)
• libuv: Upgrade to 1.4.2. See libuv ChangeLog for details of fixes.

ARM offers support for io.js on ARMv8

ARM contacted Rod Vagg, lead of the io.js Build Working Group, to offer their support to the io.js project. ARM and their hardware partners are on track to make ARMv8 a viable server platform and the nimble nature of server-side JavaScript make it a perfect fit to run on the new ARM.

Since ARMv8 is already being adopted by mobile device manufacturers, newer versions of V8 already have good support. Because of V8's pivotal role in Android, io.js is perfectly suited to track that support, and even contribute to it given our new relationships with the V8 team.

From the beginning of the io.js project, Rod has championed the role of ARM for io.js, for IoT, hobbyist, and server use. We already have ARMv6 builds of each release for devices such as Raspberry Pi. and ARMv7 builds for many more popular devices (including the Online Labs ARM-based cloud platform, who have also offered help to io.js). ARMv8 is the logical extension of this, but also has exciting potential for server-side applications, particularly given the new 64-bit support.

The build team is in the process of being given access to the Linaro ARMv8 Server Cluster for integration with the io.js CI platform, which should eventually lead to regular ARMv8 binary releases.

Community Updates

• Reconciliation Proposal: The io.js project is preparing a plan for reconciliation that can be brought to The Node.js Foundation. Input from the community is very important at this early stage so please leave a comment.
• New internal C++ Streams API: A fresh C++ Streams API landed in io.js this week, allowing you to wrap a TLS stream into another TLS stream.
• io.js Roadmap: The Roadmap is the plan for the future of io.js. It presents the plans for the stability policy, and lists what the immediate priorities for io.js as a whole are.
• Roadmap Slides Finished and Ready for Translation: The set of introductory slides for the Roadmap of io.js have been finished, and are ready for translation. Do you think you could present them to a group near you? Comment and we'll work with you to prepare you to present!
• Microsoft io.js How-To for Azure Websites: Microsoft published a how-to tutorial for their Azure platform that describes how to use io.js with Azure Websites.
• Floobits moves to io.js: The code pairing software Floobits converted their platform to io.js, in part because of frustration with Node's slower release cycle, because the inclusion of more ES6 features without the need for the --harmony flag, and because they felt changes from 0.10.0 to 0.12.0 weren't very big.
• Anand Mani Sankar's Node.js vs io.js: Why the fork?!?: Anand wrote a good, for the most part objective, post about the recent history of io.js, and what we hope to achieve with it. A good read for people who aren't engaged in the community to catch up with.
• iojs-jp - New io.js Japanese Blog: The iojs-jp community has created a localized io.js related blog to disseminate content in their language. If you're interested, take a look!
• iojs-cn - New io.js Chinese Blog: Similarly to the iojs-jp community, the iojs-cn community created a localized blog to publish posts about io.js to in their language. Make sure to visit if you're curious about iojs-cn or Chinese news about io.js!
• Roadmap Slides Review - A review of the roadmap slides before they were released to ensure they met with the message the project upholds.

io.js Support Added

• Wallby.js, a while-you-write testing library for JavaScript, hit version 1.0 and added support for io.js!
• jsdom, an implementation of the WHATWG DOM and HTML standards, just hit version 4.0.0, which added a requirement of io.js.
• give's creator tweeted that newer versions of give support io.js. Give is a git-based node.js/io.js version manager.
• The Firebase Realtime Client, the official web/node.js JavaScript client for Firebase, tweeted that they added support for io.js in version 2.2.1
• Semaphore, a hosted continuous integrations service, tweeted about added io.js support in their Platform update on February 24th, 2015.

# io.js 1.4.1 Release

_Note: version **1.4.0** was tagged and built but not released. A libuv bug was discovered in the process so the release was aborted. We have jumped to 1.4.1 to avoid confusion._

## Notable changes

* **process** / **promises**: An`'unhandledRejection'` event is now emitted on `process` whenever a `Promise` is rejected and no error handler is attached to the `Promise` within a turn of the event loop. A `'rejectionHandled'` event is now emitted whenever a `Promise` was rejected and an error handler was attached to it later than after an event loop turn.  [#758](https://github.com/iojs/io.js/pull/758) (Petka Antonov)
* **streams**: you can now use regular streams as an underlying socket for `tls.connect()` [#926](https://github.com/iojs/io.js/pull/926) (Fedor Indutny)
* **http**: A new `'abort'` event emitted when a `http.ClientRequest` is aborted by the client. [#945](https://github.com/iojs/io.js/pull/945) (Evan Lucas)
* **V8**: Upgrade V8 to 4.1.0.21. Includes an embargoed fix, details should be available when embargo is lifted. A breaking ABI change has been held back from this upgrade, possibly to be included when io.js merges V8 4.2. See [#952](https://github.com/iojs/io.js/pull/952) for discussion.
* **npm**: Upgrade npm to 2.6.0. Includes features to support the new registry and to prepare for `npm@3`. See [npm CHANGELOG.md](https://github.com/npm/npm/blob/master/CHANGELOG.md#v260-2015-02-12) for details. Summary:
  * [#5068](https://github.com/npm/npm/issues/5068) Add new logout command, and make it do something useful on both bearer-based and basic-based authed clients.
  * [#6565](https://github.com/npm/npm/issues/6565) Warn that `peerDependency` behavior is changing and add a note to the docs.
  * [#7171](https://github.com/npm/npm/issues/7171) Warn that `engineStrict` in `package.json` will be going away in the next major version of npm (coming soon!)
* **libuv**: Upgrade to 1.4.2. See [libuv ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for details of fixes.

# ARM offers support for io.js on ARMv8

ARM contacted Rod Vagg, lead of the io.js Build Working Group, to offer their support to the io.js project. ARM and their hardware partners are on track to make ARMv8 a viable server platform and the nimble nature of server-side JavaScript make it a perfect fit to run on the new ARM.

Since ARMv8 is already being adopted by mobile device manufacturers, newer versions of V8 already have good support. Because of V8's pivotal role in Android, io.js is perfectly suited to track that support, and even contribute to it given our new relationships with the V8 team.

From the beginning of the io.js project, Rod has championed the role of ARM for io.js, for IoT, hobbyist, and server use. We already have ARMv6 builds of each release for devices such as Raspberry Pi. and ARMv7 builds for many more popular devices (including the Online Labs ARM-based cloud platform, who have also offered help to io.js). ARMv8 is the logical extension of this, but also has exciting potential for server-side applications, particularly given the new 64-bit support.

The build team is in the process of being given access to the Linaro ARMv8 Server Cluster for integration with the io.js CI platform, which should eventually lead to regular ARMv8 binary releases.

# Community Updates

* [**Reconciliation Proposal**](https://github.com/iojs/io.js/issues/978): The io.js project is preparing a plan for reconciliation that can be brought to The Node.js Foundation. Input from the community is very important at this early stage so please leave a comment. 
* **New internal C++ Streams API**: A [fresh C++ Streams API](https://github.com/iojs/io.js/commit/b9686233fc0be679d7ba1262b611711629ee334e) landed in io.js this week, allowing you to wrap a TLS stream into another TLS stream. 
* **io.js Roadmap**: [The Roadmap](https://github.com/iojs/io.js/blob/v1.x/ROADMAP.md) is the plan for the future of io.js. It presents the plans for the stability policy, and lists what the immediate priorities for io.js as a whole are.
* **Roadmap Slides Finished and Ready for Translation**: The set of introductory slides for the Roadmap of io.js [have been finished, and are ready for translation](https://github.com/iojs/roadmap/issues/18). Do you think you could present them to a group near you? Comment and we'll work with you to prepare you to present! 
* **Microsoft io.js How-To for Azure Websites**: Microsoft [published a how-to](http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/) tutorial for their Azure platform that describes how to use io.js with Azure Websites.
* **Floobits moves to io.js**: The code pairing software Floobits [converted their platform to io.js](https://news.floobits.com/2015/02/23/on-moving-to-io.js/), in part because of frustration with Node's slower release cycle, because the inclusion of more ES6 features without the need for the `--harmony` flag, and because they felt changes from 0.10.0 to 0.12.0 weren't very big.
* **Anand Mani Sankar's _Node.js vs io.js: Why the fork?!?_**: Anand wrote a good, for the most part objective, [post about the recent history of io.js](http://anandmanisankar.com/posts/nodejs-iojs-why-the-fork/#.VO82hE60PVw.twitter), and what we hope to achieve with it. A good read for people who aren't engaged in the community to catch up with.
* **iojs-jp - New io.js Japanese Blog**: The iojs-jp community has created a [localized io.js related blog](http://blog.iojs.jp/) to disseminate content in their language. If you're interested, take a look!
* **iojs-cn - New io.js Chinese Blog**: Similarly to the iojs-jp community, the iojs-cn community created a [localized blog](http://cn.iojs.org/) to publish posts about io.js to in their language. Make sure to visit if you're curious about iojs-cn or Chinese news about io.js!
* **[Roadmap Slides Review](https://www.youtube.com/watch?v=etI_UD4wXlo)** - A review of the roadmap slides before they were released to ensure they met with the message the project upholds.

# io.js Support Added
* **[Wallby.js](http://wallabyjs.com/)**, a while-you-write testing library for JavaScript, hit version 1.0 and [added support for io.js](http://dm.gl/2015/02/23/wallaby-version-one/)!
* **[jsdom](https://github.com/tmpvar/jsdom)**, an implementation of the WHATWG DOM and HTML standards, just hit [version 4.0.0](https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400), which added a _requirement_ of io.js.
* **[give](https://github.com/mmalecki/give)**'s creator [tweeted](https://twitter.com/maciejmalecki/status/569629100215816192) that newer versions of give support io.js. Give is a git-based node.js/io.js version manager.
* The **Firebase Realtime Client**, the official web/node.js JavaScript client for Firebase, [tweeted](https://twitter.com/FirebaseRelease/status/570000737343647744) that they added support for io.js in [version 2.2.1](https://www.firebase.com/docs/web/changelog.html#section-realtime-client)
* **Semaphore**, a hosted continuous integrations service, [tweeted](https://twitter.com/semaphoreapp/status/570987355005431809) about added io.js support in their [Platform update on February 24th, 2015](https://semaphoreapp.com/blog/2015/02/17/platform-update-on-february-24th.html?utm_source=twitter&utm_medium=social&utm_content=platform_update_launch&utm_campaign=platformupdate). 

[bnb]

jsdom requires io.js in 4.0.0: https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400

[bnb]

Wallby.js version 1.0 supports io.js: http://dm.gl/2015/02/23/wallaby-version-one/

[kosamari]

If you're one of the few using give (https://github.com/mmalecki/give ), it now supports io.js

https://twitter.com/maciejmalecki/status/569629100215816192
https://github.com/mmalecki/give

[kosamari]

Yay, new internal C++ Streams API just landed in io.js: nodejs/node@b968623 … . Now you can wrap TLS stream into another TLS stream!

https://twitter.com/indutny/status/569591801251831808

[kosamari]

@mikeal @bnb I actually work for a company that makes social mention monitoring platform. Those 2 ^^ & jsdom news seems to be trending tweets over the weekend.

In addition to us searching the web, maybe tweet from @official_iojs "if your project support io.js, let us know and we'll include in our weekly" or something??

[bnb]

@kosamari That's a good idea. Should it be a weekly reminder? Monthly? Or just one time?

[segphault]

Microsoft published documentation that demonstrates how to run io.js on Azure: http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/

[bnb]

Version 2.2.1 of Firebase web/Node.js client supports io.js.
https://www.firebase.com/docs/web/changelog.html#section-realtime-client
https://twitter.com/FirebaseRelease/status/570000737343647744

[mikeal]

semaphore support https://twitter.com/semaphoreapp/status/570987355005431809

[mikeal]

Floobits moves to io.js https://news.floobits.com/2015/02/23/on-moving-to-io.js/

[mikeal]

http://anandmanisankar.com/posts/nodejs-iojs-why-the-fork/#.VO82hE60PVw.twitter

[dotproto]

Cross linking with the relevant website issue: nodejs/iojs.org#241

[mikeal]

1.4.1 https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md

io.js roadmap officially merged https://github.com/iojs/io.js/blob/v1.x/ROADMAP.md

established tracing, roadmap, evangelism and i18n working group charters nodejs/node@ae7a233

roadmap slides ready for translators and speakers nodejs/roadmap#18

reconciliation proposal nodejs/node#978

[rvagg]

What time is this due to go out? I have some very interesting news I think I can share on behalf of build. Just not at this instant.

[mikeal]

in like 12 - 16 hours :)

[bnb]

@rvagg You should have time to get it done. As Mikeal said, it'll be in a while. Looking forward to your news.

[mikeal]

io.js japenese blog is up http://blog.iojs.jp/

[popomore]

Here is Chinese blog http://cn.iojs.org/

[bnb]

Writing this now.

• io.js Releases
• Notable Events in the Community
• io.js Support Added
• io.js WG Meetings
• Get involved!

[bnb]

Links in order of type:

io.js Updates

• https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md
• Reconciliation Proposal node#978
• https://twitter.com/indutny/status/569591801251831808
• https://github.com/iojs/io.js/blob/v1.x/ROADMAP.md
• Roadmap Translations and Speakers roadmap#18

Notable Events and Posts in the Community

• http://azure.microsoft.com/en-us/documentation/articles/web-sites-nodejs-iojs/
• https://news.floobits.com/2015/02/23/on-moving-to-io.js/
• http://anandmanisankar.com/posts/nodejs-iojs-why-the-fork/#.VO82hE60PVw.twitter
• http://blog.iojs.jp/
• http://cn.iojs.org/

io.js Support Added

• http://dm.gl/2015/02/23/wallaby-version-one/
• https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400
• https://twitter.com/maciejmalecki/status/569629100215816192 + https://github.com/mmalecki/give
• https://twitter.com/FirebaseRelease/status/570000737343647744 + https://www.firebase.com/docs/web/changelog.html#section-realtime-client
• https://twitter.com/semaphoreapp/status/570987355005431809

io.js TC/WG meetings

• https://www.youtube.com/watch?v=etI_UD4wXlo

[bnb]

@rvagg I'm writing it now. Will you be able to get that update to us sometime soon?

[Fishrock123]

maybe change io.js Official Updates to just io.js Updates?

Or, like https://medium.com/node-js-javascript/io-js-week-of-february-20th-2015-48486615980, a release 1.4.1 section?

[bnb]

io.js 1.4.1 Release

Note: version 1.4.0 was tagged and built but not released. A libuv bug was discovered in the process so the release was aborted. We have jumped to 1.4.1 to avoid confusion.

Notable changes

• process / promises: An'unhandledRejection' event is now emitted on process whenever a Promise is rejected and no error handler is attached to the Promise within a turn of the event loop. A 'rejectionHandled' event is now emitted whenever a Promise was rejected and an error handler was attached to it later than after an event loop turn. #758 (Petka Antonov)
• streams: you can now use regular streams as an underlying socket for tls.connect() #926 (Fedor Indutny)
• http: A new 'abort' event emitted when a http.ClientRequest is aborted by the client. #945 (Evan Lucas)
• V8: Upgrade V8 to 4.1.0.21. Includes an embargoed fix, details should be available when embargo is lifted. A breaking ABI change has been held back from this upgrade, possibly to be included when io.js merges V8 4.2. See #952 for discussion.
• npm: Upgrade npm to 2.6.0. Includes features to support the new registry and to prepare for npm@3. See npm CHANGELOG.md for details. Summary:
  • #5068 Add new logout command, and make it do something useful on both bearer-based and basic-based authed clients.
  • #6565 Warn that peerDependency behavior is changing and add a note to the docs.
  • #7171 Warn that engineStrict in package.json will be going away in the next major version of npm (coming soon!)
• libuv: Upgrade to 1.4.2. See libuv ChangeLog for details of fixes.

io.js Updates

• Important: Reconciliation Proposal: The Reconciliation Proposal landed on the 26th, and is a very important milestone for io.js in rejoining Node.js as a unified front. The Reconciliation Proposal outlines Technical Governance, outlines a plan for joined Long Term Support, how the versions of the two projects will merge, and the choice each of the WGs would have were a merger to occur.
• New internal C++ Streams API: A fresh C++ Streams API landed in io.js this week, allowing you to wrap a TLS stream into another TLS stream.
• io.js Roadmap: The Roadmap is the plan for the future of io.js. It presents the plans for the stability policy, and lists what the immediate priorities for io.js as a whole are.
• Roadmap Slides Finished and Ready for Translation: The set of introductory slides for the Roadmap of io.js have been finished, and are ready for translation. Do you think you could present them to a group near you? Comment and we'll work with you to prepare you to present!

# io.js 1.4.1 Release

_Note: version **1.4.0** was tagged and built but not released. A libuv bug was discovered in the process so the release was aborted. We have jumped to 1.4.1 to avoid confusion._

## Notable changes

* **process** / **promises**: An`'unhandledRejection'` event is now emitted on `process` whenever a `Promise` is rejected and no error handler is attached to the `Promise` within a turn of the event loop. A `'rejectionHandled'` event is now emitted whenever a `Promise` was rejected and an error handler was attached to it later than after an event loop turn.  [#758](https://github.com/iojs/io.js/pull/758) (Petka Antonov)
* **streams**: you can now use regular streams as an underlying socket for `tls.connect()` [#926](https://github.com/iojs/io.js/pull/926) (Fedor Indutny)
* **http**: A new `'abort'` event emitted when a `http.ClientRequest` is aborted by the client. [#945](https://github.com/iojs/io.js/pull/945) (Evan Lucas)
* **V8**: Upgrade V8 to 4.1.0.21. Includes an embargoed fix, details should be available when embargo is lifted. A breaking ABI change has been held back from this upgrade, possibly to be included when io.js merges V8 4.2. See [#952](https://github.com/iojs/io.js/pull/952) for discussion.
* **npm**: Upgrade npm to 2.6.0. Includes features to support the new registry and to prepare for `npm@3`. See [npm CHANGELOG.md](https://github.com/npm/npm/blob/master/CHANGELOG.md#v260-2015-02-12) for details. Summary:
  * [#5068](https://github.com/npm/npm/issues/5068) Add new logout command, and make it do something useful on both bearer-based and basic-based authed clients.
  * [#6565](https://github.com/npm/npm/issues/6565) Warn that `peerDependency` behavior is changing and add a note to the docs.
  * [#7171](https://github.com/npm/npm/issues/7171) Warn that `engineStrict` in `package.json` will be going away in the next major version of npm (coming soon!)
* **libuv**: Upgrade to 1.4.2. See [libuv ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for details of fixes.

# io.js Updates

* **Important: Reconciliation Proposal**: The [Reconciliation Proposal](https://github.com/iojs/io.js/issues/978) landed on the 26th, and is a very important milestone for io.js in **rejoining Node.js** as a unified front. The Reconciliation Proposal outlines Technical Governance, outlines a plan for joined Long Term Support, how the versions of the two projects will merge, and the choice each of the WGs would have were a merger to occur.
* **New internal C++ Streams API**: A [fresh C++ Streams API](https://github.com/iojs/io.js/commit/b9686233fc0be679d7ba1262b611711629ee334e) landed in io.js this week, allowing you to wrap a TLS stream into another TLS stream. 
* **io.js Roadmap**: [The Roadmap](https://github.com/iojs/io.js/blob/v1.x/ROADMAP.md) is the plan for the future of io.js. It presents the plans for the stability policy, and lists what the immediate priorities for io.js as a whole are.
* **Roadmap Slides Finished and Ready for Translation**: The set of introductory slides for the Roadmap of io.js [have been finished, and are ready for translation](https://github.com/iojs/roadmap/issues/18). Do you think you could present them to a group near you? Comment and we'll work with you to prepare you to present! 

[mikeal]

@bnb I updated the description with your content.

[mikeal]

I'd like to re-word the Reconciliation post text to stick with just the facts.

• Reconciliation Proposal: The io.js project is preparing a plan for reconciliation that can be brought to The Node.js Foundation. Input from the community is very important at this early stage so please leave a comment.

[bnb]

io.js TC/WG meetings

• Roadmap Slides Review - A review of the roadmap slides before they were released to ensure they met with the message the project upholds.

# io.js TC/WG meetings
* **[Roadmap Slides Review](https://www.youtube.com/watch?v=etI_UD4wXlo)** - A review of the roadmap slides before they were released to ensure they met with the message the project upholds.

[mikeal]

I'm gonna stick the Roadmap Slides Review in to the rest of the update so that we don't have a section with only one item

[bnb]

@mikeal Okay, no problem. Update the page, as I just updated the first post.

[bnb]

@mikeal Can you get into contact with @rvagg to see if he still wants to add his thing?

[rvagg]

/cc @iojs/build who I don't think I've shared this with yet because it's been a private conversation so far.

I don't know if this goes with the style of what you're publishing but here's my prose:

ARM contacted Rod Vagg as representative of the io.js Build Working Group to offer their support to the io.js project. ARM and their hardware partners are on track to make ARMv8 a viable server platform and the nimble nature of server-side JavaScript make it a perfect fit. Unfortunately, there is little they can do with the current Node.js codebase given its old V8 version, which does not include proper support for ARMv8 hardware. Since ARMv8 is being targeted at mobile device manufacturers, newer versions of V8 already have good support. Because of its pivotal role in Android, io.js is perfectly suited to track that support and even contribute to it given our new relationships with the V8 team.
From the beginning of the io.js project, Rod has championed the role of ARM for io.js, for both IoT, hobbyist and server use. We already have ARMv6 builds for each release for devices such as Raspberry Pi and ARMv7 builds for many more popular devices (including the Online Labs ARM-based cloud platform, who have also offered help to io.js). ARMv8 is the logical extension of this but has exciting potential for server-side applications, particularly given the new 64-bit support.
The build team is in the process of being given access to the Linaro ARMv8 Server Cluster for integration with the io.js CI platform which should eventually lead to regular ARMv8 binary releases.
TL;DR io.js + ARMv8 FTW, this is very exciting and having ARM reach out to us is just another example of the amazing traction io.js has garnered in such a short amount of time and a validation of our development and governance model.

[bnb]

@rvagg I made a few nit-picky changes to it to make it 100% structurally sound. I've highlighted those with Markdown's inline code styling below. Would you look at the inline code bits below and make sure everything seems right to you?

I only made a few word changes, but I want to make sure you're still satisfied with the meaning of it. I completely understand if you don't have the time and/or desire to go through it--if that's the case, just let me know and I'll have another Evangelism team member look it over.

---

ARM contacted Rod Vagg as representative of the io.js Build Working Group to offer their support to the io.js project. ARM and their hardware partners are on track to make ARMv8 a viable server platform and the nimble nature of server-side JavaScript make it a perfect fit to run on the new ARMv8.

Unfortunately, there is little ARM can do with the current Node.js codebase, given its old V8 version, which does not include proper support for ARMv8 hardware. Since ARMv8 is being targeted at mobile device manufacturers, newer versions of V8 already have good support. Because of V8's pivotal role in Android, io.js is perfectly suited to track that support, and even contribute to it given our new relationships with the V8 team.

From the beginning of the io.js project, Rod has championed the role of ARM for io.js, for IoT, hobbyist, and server use. We already have ARMv6 builds of each release for devices such as Raspberry Pi. and ARMv7 builds for many more popular devices (including the Online Labs ARM-based cloud platform, who have also offered help to io.js). ARMv8 is the logical extension of this, but also has exciting potential for server-side applications, particularly given the new 64-bit support.

The build team is in the process of being given access to the Linaro ARMv8 Server Cluster for integration with the io.js CI platform, which should eventually lead to regular ARMv8 binary releases.

TL;DR io.js + ARMv8 FTW, this is very exciting and having ARM reach out to us is just another example of the amazing traction io.js has garnered in such a short amount of time and a validation of our development and governance model.

[rvagg]

@bnb that's fine, but perhaps revisit the end of the first paragraph, not sure repeating "ARMv8" is optimal there but I'll leave the end decision to you. Cheers.

[bnb]

@rvagg Thanks for noticing that. Mikeal edited it a bit more, and it's been included in the post at the top. Thanks for sharing it with us--it's really awesome.

[bnb]

Just went over it again, LGTM.

[mikeal]

Published https://medium.com/node-js-javascript/io-js-week-of-february-17th-9422a589302a

Ready for translations :)

[alexpods]

@mikeal must be february 27th, not 17th. But who cares..

[bnb]

Yes, it's Feb 27th 📅

[rosskukulinski]

@mikeal - is there a place for translations of this to go? If the EN-US is posted to medium.com/nodej-js-javascript, then where should the translations reside?

[mikeal]

@rosskukulinski we leave that up to each community and encourage them to use whatever service they think will reach the most people in their community :)

[rvagg]

ugh, this wasn't intended but:

Since ARMv8 is being targeted at mobile device manufacturers ..

should probably be

Since ARMv8 is already being adopted by mobile device manufacturers ..

ARM want this to be seen as a viable server platform (as do we frankly) rather than "targeting mobile".

[mikeal]

cool, i'll update the medium post if someone else can update here.

[bnb]

Updated in rendered and template parts of the first post.

[julianduque]

@mikeal is there a way to get the full markdown version, that will be easier for translation groups

[mikeal]

@julianduque look at the bottom of the Issue description :)

[bnb]

@julianduque As Mikeal said, it's at the bottom. It should be like that for every Weekly Update, and they should be in ./weekly-updates soon after they're published.

[julianduque]

@mikeal @bnb perfect, thanks for the heads up :)