Hacker News new | past | comments | ask | show | jobs | submit login

does the io.js fork still exist?

If it is merged back into the main project or left unmaintained the fork failed and died.




You are implying that the only measure of success for a fork is for it to exist indefinitely. If the goal of io.js was to improve Node's governance model, which appears to be the case, then I would consider it a success.


> Forks of a large project seldom survive.

The fork died.

that is the point. goal or no goal.


It obviously didn't die. It got merged into the original project. That is a great end of a fork.


So it didn't survive then. Isn't that the whole point of what I said:

> Forks of a large project seldom survive.


But it did survive. I can't view rejoining the forked from repository as dying.


Who is still using the io.js fork? Nobody?

That is my point.


Everyone who is using node.js is using it... Anyway you and I have a different idea of what it means to die. The identifier io.js is no longer in use. But everything that it actually is, is now node.js.


ok but that's a terrible point


terrible or not my point still stands, and it is a truer point now that nobody is using the fork that was io.js.


If the primary goals behind the fork were achieved, to say that it failed and died (when it was actually reintegrated) is far from an accurate claim.


If the fork achieved it's goals then it was a success.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: