Io.js – What You Need to Know
gist.github.com
Io.js – What You Need to Know
1–10 of 17 posts
Re: Io.js – What You Need to Know
#2From what I can see the main differences with node.js is pulling more regularly from V8 and using semantic versioning. Are there any more differences?
Re: Io.js – What You Need to Know
#3The 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 without their involvement. What's the difference here.
That's pretty antagonistic IYAM.
Re: Io.js – What You Need to Know
#4From what I can see the main differences with node.js is pulling more regularly from V8 and using semantic versioning. Are there any more differences?
As a recent convert to Node who switched to it because I thought we'd be closing in on 1.0 this year and instead got ... crickets. For my part, "pulling more regularly from V8" is enough all by itself.
Re: Io.js – What You Need to Know
#5From what I can see the main differences with node.js is pulling more regularly from V8 and using semantic versioning. Are there any more differences?
The trademark is in the public domain which means it can never be sold. A company such as Oracle acquiring Joyent (and thus owning NodeJS) is a very realistic possibility, if not inevitable. You don't need anyones permission to use "iojs". You may use it for a book title, conference, training course, or service without needing permission or paying anyone to use it.
iojs follows an open governance model which means that large US corporations have equal input to everyone else on the direction iojs heads. Not any more or any less.
Edit: I would like to clarify that my opinion is not in any way based on Joyent not fulfilling their duty to the public. I am a former employee at Joyent and I have nothing but respect and praise for the work they have done WRT NodeJS. I hope to see NodeJS continue to thrive under Joyent's guidance. That said, I am supportive of an open initiative that iojs is attempting to achieve. I believe there are some long term benefits to having a release that is completely sheltered from any corporate initiative. My view is not meant to be antagonistic toward Joyent nor any of the NodeJS contributors.
Re: Io.js – What You Need to Know
#6The 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…
Fedor kind of started the whole thing, though. http://www.infoworld.com/article/2855057/application-develop...
Re: Io.js – What You Need to Know
#7The 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.
Re: Io.js – What You Need to Know
#8So can we say Joyent blew it with too much corporatism?
Re: Io.js – What You Need to Know
#9The 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.
> I agree .. this is basically what Rocket is doing is response to the commercial support of Docker.
What? That's what came away with? Even shykes didn't accuse them of that.
Re: Io.js – What You Need to Know
#10The 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?