Repository navigation
The relationship to node.js is confusing #3
Description
Activity
Also, the README instructs to download pre-compiled binaries from node.js.org/download
Is this the new name of lib uv?
Oh. This is node 0.12 source code. Is this is a node fork?
Yes. And just look at the people who've send PRs.
Looking at the commit history, they are pulling in changes from Joyent's repo as well.
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
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.
There is some information in the discussion here: https://news.ycombinator.com/item?id=8669557
@rsp: I don't see any committers contributing there. Could you possibly point to a specific comment? Looks like speculation to me :(
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.
A formal statement will probably be made soon. To my knowledge the TC / Advisory board have regular meetings and and some statement about
io.jswill 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.jstrademark to the community, then so be it.Keep the speculation/drama on hackernews please, this is an inappropriate place for it.
39 remaining items
- added a commit that references this issue
on Dec 15, 2017 - added a commit that references this issue
on Dec 15, 2017 - added 2 commits that reference this issue
on Jan 8, 2018 - added a commit that references this issue
on Jan 23, 2018 - added a commit that references this issue
on Jan 24, 2018 - added a commit that references this issue
on Nov 21, 2022 - added a commit that references this issue
on Mar 20, 2026 - added a commit that references this issue
on Jun 2, 2026 - added a commit that references this issue
on Jun 18, 2026 - added a commit that references this issue
on Jun 25, 2026 - added a commit that references this issue
on Jul 16, 2026 - added a commit that references this issue
on Jul 30, 2026
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.