-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nodejs & io.js merge? What now? #3475
Comments
I'll see how they'll deal with v8. One of the reason NW chose IO.js is that the v8 version is updated. Our integration requires that Node uses a similar v8 version with Chromium. V8 upgrades fast with Chromium updates and it doesn't have any stable API... |
See also nodejs/node#1451 which currently block us to update to Chromium 44. |
io,js seems to offer significant speed improvements over nodejs, benchmarks I saw were done with server tests/benches - not entirely representative. Interesting thread @rogerwang , i believe nwjs set out to build against newer versions of chromium etc for future releases, so sticking with io.js is going to make that possible until node starts building against latest v8 too. |
Closing. |
Just read http://venturebeat.com/2015/05/13/node-project-spinoff-io-js-is-moving-to-the-node-js-foundation-with-a-merge-in-progress/
"In a major step toward reconciliation with the open-source project for trendy server-side JavaScript framework Node.js, the technical committee in charge of the Io.js group, which split off from the Node project several months ago, today voted to join the Node.js Foundation."
Any thoughts / ideas if we'll see nodejs for nwjs13 or is it too early to switch back ?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: