Split nodejs

JS Adventure Continues! Last week there was a significant event that led to the appearance of the fork of nodejs. Unresolved project problems gained a critical mass and led to a split: some of the main developers who were dissatisfied with Joyent’s policy regarding the development of the project created a fork and left the project. In particular, they are dissatisfied with the fact that since 2013 (version 0.10) the project has practically not developed, it uses the old version of v8, and the versioning system has become confusing and does not correspond to the generally accepted semver model and in general. And so, meet io.js.

The new project has already gathered an audience and is preparing to release the first release version on January 13. According to the developers, the project will be node-compatible. True, only to version 1.0, which is actually going to be released within a specified time. And the project will not be managed by a private company, but by an interested community, for which the fork was actually created. New commits related to updating v8 and js-libraries are already appearing in the project.

If we recall the departure from the TJ Holowaychuck project, the picture for Joyent is disappointing: the project loses the best developers. And for the entire nodejs community is ambiguous. Let's see what happens.