Skip to content
This repository has been archived by the owner on Aug 1, 2019. It is now read-only.

Evangelism: Weekly Update for May 15th #71

Closed
Gioyik opened this issue May 8, 2015 · 18 comments
Closed

Evangelism: Weekly Update for May 15th #71

Gioyik opened this issue May 8, 2015 · 18 comments

Comments

@Gioyik
Copy link
Contributor

Gioyik commented May 8, 2015

What's up for this week?

@julianduque julianduque changed the title Evangelism: Weekly Update for next week Evangelism: Weekly Update for May 15th May 8, 2015
@a0viedo
Copy link
Member

a0viedo commented May 12, 2015

Performance Showdown: Node.js vs. io.js v2.0.0 https://raygun.io/blog/2015/05/performance-showdown-node-js-vs-io-js-v2-0-0/

@yosuke-furukawa
Copy link
Member

Microsoft forks node.js and they replace v8 to their Chakra Engine. https://github.com/Microsoft/node

@a0viedo
Copy link
Member

a0viedo commented May 13, 2015

@yosuke-furukawa maybe the blog post could give more insight

@mikeal
Copy link
Contributor

mikeal commented May 13, 2015

with all the drama around "forks" I would call this something else :) it's intention is not to split development or the community, but to show what using node w/ Chakra is like ;)

@yosuke-furukawa
Copy link
Member

TC members decide to move io.js to Node Foundation.
And the organization name will be renamed nodejs.
https://twitter.com/rvagg/status/598605393636429825

@yosuke-furukawa
Copy link
Member

@a0viedo Yay, the blog post is really helpful.

So we will list the news like following sentence.
Microsoft brings Node.js to Windows IoT core, and they fork joyent/node and replace v8 to Chakra.

@rvagg
Copy link
Member

rvagg commented May 14, 2015

re microsoft "forking", I'd suggest using much gentler language than that, if you do a diff between their work and 0.12 and exclude the chakra shim then it boils down to a few lines of changed code which could easily be merged back in to core so there's zero drama and only upside

@yosuke-furukawa
Copy link
Member

Oh, I didn't understand fork is a sensitive word.
So... " they will propose that node can choose JavaScript backend including Chakra optionally. "

@rvagg
Copy link
Member

rvagg commented May 14, 2015

Further context that may be helpful: this is targeting Windows 10 only (atm, not sure if it'll ever work lower than that) and gives Node users the ability to use Windows 10 on small devices. Recall that Microsoft have announced that Windows 10 even works on Raspberry Pi now, I believe it's now being named "Windows 10 IoT Core", see http://www.anandtech.com/show/9250/microsoft-details-windows-10-editions for current updates on the editions. This "port" is likely the only way to run Node on any of these devices if they are running Windows 10. They want Windows 10 to actually be useful and Node is part of that story.

Chakra is written in C and they have written a shim layer that sits on top of that and presents the V8 C++ API so Node doesn't need to be changed to talk to this.

Perhaps this should be a blog post ...

@Gioyik
Copy link
Contributor Author

Gioyik commented May 15, 2015

{node,io}.js benchmark graphs http://thlorenz.com/benchgraph/

@Gioyik
Copy link
Contributor Author

Gioyik commented May 15, 2015

No release this week, how we should name the WU for this week?

@julianduque
Copy link
Contributor

@Gioyik yes! only community updates and events

@Gioyik
Copy link
Contributor Author

Gioyik commented May 15, 2015

Ok, I created a PR #75. So this get frizzed. Something to add? let's discuss it for next week on #73.

Please review the PR!

@yosuke-furukawa
Copy link
Member

@julianduque Landed, Would you post our weekly updates on the medium ??

@julianduque
Copy link
Contributor

@yosuke-furukawa
Copy link
Member

@julianduque
I cannot see the news on medium....

https://github.com/nodejs/evangelism/blob/master/weekly-updates/weekly-update.2015-05-15.md#iojs-news

https://medium.com/node-js-javascript/io-js-week-of-may-15th-9ada45bd8a28

io.js News

We are happy to announce this news, "io.js decides to join the Node Foundation". And our organization name will be renamed nodejs.

As a first step, we will move from iojs organization to nodejs organization and will converge joyent/node gradually. We will continue to release io.js until the convergence have done.

If you would like to see the convergence plan in detail, please check it at jasnell repo. When you would like to ask questions, feel free to ask @Fishrock123. The discussion log is here.

@julianduque
Copy link
Contributor

@yosuke-furukawa sorry, I was looking at a different branch, I updated the article

@yosuke-furukawa
Copy link
Member

@julianduque Thank you! I confirmed!!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants