Comments (30)
Also, the README instructs to download pre-compiled binaries from node.js.org/download
from node.
Is this the new name of lib uv?
from node.
Oh. This is node 0.12 source code. Is this is a node fork?
from node.
This is node 0.12 source code.
@arunoda Are you sure?
from node.
Yes. And just look at the people who've send PRs.
from node.
Looking at the commit history, they are pulling in changes from Joyent's repo as well.
from node.
@arunoda Glad to know.
I can't wait to see v0.12
.
from node.
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
from node.
It's nice to see @indutny in action :)
from node.
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.
from node.
There is some information in the discussion here: https://news.ycombinator.com/item?id=8669557
from node.
@rsp: I don't see any committers contributing there. Could you possibly point to a specific comment? Looks like speculation to me :(
from node.
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.
from node.
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.
from node.
Keep the speculation/drama on hackernews please, this is an inappropriate place for it.
from node.
I heard that node.js
was a trademark but not node
itself so perhaps a more appropriate name could be chosen. io.js
is kind of lame, everybody knows node
. Make it node foundation
, node.org
or something. :)
from node.
@Rush tell it to Joyent, we don't have any control over them putting it in a foundation and we can't call it anything with "node" in it or Joyent says they'll come after us for trademark violation.
from node.
@mikeal Is there any place where we could read some info on who is behind the fork, what is the position of Joyent and npm, Inc. regarding it, what is the plan about compatibility with Joyent's Node.js and npm modules and the registry, whether it is a fork of https://github.com/joyent/node or https://github.com/node-forward/node and any other useful information on what the fork can mean to the community?
I've found https://github.com/iojs/io.js/blob/master/doc/tc-meetings/2014-10-09.md but the issue https://github.com/node-forward/node/issues/2 that is referenced there is a dead link and the video https://www.youtube.com/watch?v=fNW_tu2QnpA was made private so most of the context is missing.
The discussion on Hacker News is mostly just speculation, the website https://github.com/iojs/iojs.github.io is an empty repo, the iojs organization has no public members, and all of the secrecy results in lots of rumors and speculation.
Is there any public discussion that is taking place? When can we expect any official answers to the question that people are asking about the fork? Thanks.
from node.
Expect more information this week, there's a few complicated background events that need to happen before there can be full information flow but rest assured that the goal of everyone involved here is to achieve complete openness. Patience please.
from node.
@rvagg OK, I'll keep waiting. Thanks for the info.
from node.
Sorry guys, I may have tweeted this kinda early https://twitter.com/devongovett/status/538131893682569216 (HN post came after that tweet). Apologies if I messed up your launch plans. 😄
from node.
what ? what,,,,What happened ?
from node.
hopefully this makes it less confusing #24
from node.
https://libav.org/about.html, a fork of ffmpeg has a good intro
Libav is a friendly and community-driven effort to provide its users with a set of portable, functional and high-performance libraries for dealing with multimedia formats of all sorts. It originates from the FFmpeg codebase, but goes its own way these days, providing its users with reliable releases and a clear vision how to go forward.
from node.
Somebody set up us the bomb
from node.
@mikeal Do you think it is a good idea to put the 0.12 branch with the updated readme as the default one? It's still a bit confusing that you get to the repo and you don't see the messaging in the master branch.
from node.
@mikeal -- Why not take the npm, Inc. tact to avoid trademark concerns. "node-forward" could have changed its name to "nf" and claimed it meant "not-forking". npm is disingenuous in their claim that npm doesn't mean "node package manager", and yet they get away with it without trademark worries. Makes me wonder why the "nf" team couldn't have the same success: "nf does not mean Node Forward, but is a backronym for 'not forking', we are taking node foward into the future." Then your github page could say, "nf(1) - node forward" just like NPM does when they're talking out of the other side of their mouths: https://github.com/npm/npm#npm1----node-package-manager (oops, I guess it does officially mean "node package manager", someone contact Joyent to initiate trademark agressions)
from node.
@derekm
Calling npm "disingenuous" seems a tad harsh. Our point when saying that "npm" isn't an acronym isn't that we're trying to disclaim our Node heritage or get around trademark issues, it's that npm has a broader audience now that it's used so heavily in client-side development, and we're reflecting that changed audience in how we think about and discuss the project / product / company. Case in point: your link into the readme no longer works, because we've changed the synopsis from "Node" to "JavaScript" as soon as we noticed that it still said Node.
The reasoning behind the io.js name and why the fork happened now and not some other time is discussed in greater detail elsewhere, so I'm not too worried about the legalistic implications of what you wrote, but I did want to be clear that we're not trying to put one over on everybody. npm is the package manager for Node, but it's more than that as well.
from node.
Can this be closed? I think the relationship with Node.js has been pretty well established by now.
from node.
Yes, I do believe so. I'll close the issue.
from node.
Related Issues (20)
- require URLs HOT 4
- flaky: parallel/test-filehandle-close
- flaky: benchmark/test-benchmark-crypto HOT 1
- Cannot install Node20.12.2 Windows ARM (VMWare on M1 Mac) [fixed by uninstalling x64 first] HOT 1
- Tracking issue: compile cache HOT 1
- Tracking issue: require(esm) HOT 1
- Deadlock with worker threads and TLS `createSecureContext`
- node22 performance degradation HOT 7
- websocket HOT 4
- Inspector not starting with --watch flag before HOT 2
- [22 regression] Infinite recursion when setting `stat.atime` HOT 4
- [22 regression] Breaks gulp with `Cannot assign to read only property 'atime' of object '#<Stats>'` HOT 3
- Expose `process.env.NODE_OPTIONS` parser to user land HOT 2
- v22.0.0 breaks --v8-lite-mode build missing action for js-to-wasm-tq-csa.cc HOT 2
- Is `vcbuild` really needed
- `vm`: `constants` is undefined HOT 4
- Allow bailing early when test fails HOT 8
- Inconsistent presence of property in contextified object HOT 3
- Watch does not debounce restart when different files are updated within the debounce period
- gyp ERR! stack RangeError: Maximum call stack size exceeded HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node.