The relationship to node.js is confusing

[javajosh]

Hello. I couldn't find any mention of why this project exists apart from node.js. Would love to get some clarification on that. Thanks.

[andrewk]

Also, the README instructs to download pre-compiled binaries from node.js.org/download

[arunoda]

Is this the new name of lib uv?

[arunoda]

Oh. This is node 0.12 source code. Is this is a node fork?

[crzidea]

This is node 0.12 source code.

@arunoda Are you sure?

[arunoda]

Yes. And just look at the people who've send PRs.

[Albert-IV]

Looking at the commit history, they are pulling in changes from Joyent's repo as well.

[crzidea]

@arunoda Glad to know.
I can't wait to see v0.12.

[askmike]

This repo is the result of a lot of discussion in the node community about how well Joyent is performing its role.

• Some context: https://gigaom.com/2013/12/02/slap-fight-in-node-js-land/
• this repo on HN: https://news.ycombinator.com/item?id=8669557

[Rush]

It's nice to see @indutny in action :)

[jbergstroem]

I think this issue would benefit from silence until people being part of the fork are in a position to talk about it. Until then, what others (like me) say is at best hearsay or speculation.

[rsp]

There is some information in the discussion here: https://news.ycombinator.com/item?id=8669557

[jbergstroem]

@rsp: I don't see any committers contributing there. Could you possibly point to a specific comment? Looks like speculation to me :(

[rashthedude]

This would have been kept as a private repo if no clarifications are in place yet. I do understand that there is a power struggle in the community and some things that we could without but if nothing is done to address it then nodejs will be losing as a consequence of it. Time to pull in the same direction, ignore egocentric behaviors and drop ulterior motives for that matter.

[yoshuawuyts]

A formal statement will probably be made soon. To my knowledge the TC / Advisory board have regular meetings and and some statement about io.js will probably be at the top of the agenda.

As for a power struggle: all of this is just the community unchaining themselves from Joyents corporate agenda. If a rebranding most occur because Joyent won't hand over the node.js trademark to the community, then so be it.

[max-mapper]

Keep the speculation/drama on hackernews please, this is an inappropriate place for it.