Does Io.js offer more performance than Node.js?
Io.js – What You Need to Know
11–17 of 17 posts
Re: Io.js – What You Need to Know
#12The author seems like an optimist, but "many core contributors will help maintain both node.js and io.js" seems to disagree with reality, since indutny has been landing PRs to node only in the forks. He's a core contributor. If he needs sign-off or whatever, it's not like he doesn't have friends in all the forks. I'm pre-emptively calling bullshit on anyone who invokes the Joyent bogeyman here; tons of PRs land witho…
I agree .. this is basically what Rocket is doing is response to the commercial support of Docker. I haven't seen what tangible value io.js or Rocket are going to add. It's basically 'we aren't a corporation' and that doesn't add value by itself. If they want to look at a good example of a clone that has added value they should look at Mono/Xamarin.
Frequent releases add value,
Faster integration of v8 updates add value.
It's not as simple as you state.
Re: Io.js – What You Need to Know
#13So can we say Joyent blew it with too much corporatism?
We could say that the community wants to "move fast and break things", and (they feel that?) Joyent doesn't.
Re: Io.js – What You Need to Know
#14Does Io.js offer more performance than Node.js?
Although "more performance" doesn't mean much, the short answer is: maybe, yes.
They want to keep up to date with v8 better. Newer v8 could outperform older v8. node's is pretty old (2012) apparently.
Re: Io.js – What You Need to Know
#15Does Io.js offer more performance than Node.js?
Although "more performance" doesn't mean much, the short answer is: maybe, yes. They want to keep up to date with v8 better. Newer v8 could outperform older v8. node's is pretty old (2012) apparently.
So IO.js will update to V8 Turbofan when its released?
Re: Io.js – What You Need to Know
#16Earlier quoted context omitted.
Although "more performance" doesn't mean much, the short answer is: maybe, yes. They want to keep up to date with v8 better. Newer v8 could outperform older v8. node's is pretty old (2012) apparently.
So IO.js will update to V8 Turbofan when its released?
I thought you were being facetious! In case anyone else also thought that, turbofan is a real thing: " [1]
> Recently, Google engineers landed a new optimizing JavaScript compiler for V8, codenamed TurboFan. As the name implies, this is supposed to further improve JavaScript execution speed, likely to be better than its predecessor, Crankshaft. While TurboFan is still in its early stage, that doesn’t mean we can’t take a look at it.
I imagine that it has to get stable for v8 first before it is even considered, but that's exactly the example of potential "more performance" in io.js
[1] http://ariya.ofilabs.com/2014/08/javascript-and-v8-turbofan....
Re: Io.js – What You Need to Know
#17The author seems like an optimist, but "many core contributors will help maintain both node.js and io.js" seems to disagree with reality, since indutny has been landing PRs to node only in the forks. He's a core contributor. If he needs sign-off or whatever, it's not like he doesn't have friends in all the forks. I'm pre-emptively calling bullshit on anyone who invokes the Joyent bogeyman here; tons of PRs land witho…
I'm not following your argument. They stated "many core contributors" not "all core contributors". Obviously some people will only work with one project or the other. Could you clarify?
No, because it's perfectly clear. But perhaps I can restate: indutny's behaving in bad faith, which should be perfectly obvious to anyone. Max Ogden (the original and unofficial author of the opinion posted above) would like to believe there is no antagonism here.
If this were just some third party, perhaps this wouldn't be significant. But indutny's on node core, the technical committee, the advisory board meetings, and is the original forker of io.js. His actions are central here.