A lot of confusion about why this is going on. My take as a very interested user who has been actively tracking down info about this Node's next release and pos

A lot of confusion about why this is going on. My take as a very interested user who has been actively tracking down info about this Node's next release and possible fork for some time is this: Node.js's last supported release uses such an old version of Google's V8 that this V8 version is itself no longer supported. This, in my opinion, is just not good enough. In my personal experience, when a release cycle gets that fucked up there's a reason. Joyent hasn't shared what the reason actually is for the delay, but so many of the top contributors think they can do better with a fork, and I'm going to give them the benefit of the doubt. The plan is to do weekly releases, semver, to keep absolutely up to date with Google V8, and incidentally to not let just one interested party dictate their future directions. It's a good plan and if they follow through, I'm definitely on board.