3 ms·

the iojs site mentioned nothing about the merge as I checked yesterday, neither does nodejs site, which is a bit odd. the new version number is using iojs inst

by ausjke 11y ago

the iojs site mentioned nothing about the merge as I checked yesterday, neither does nodejs site, which is a bit odd. the new version number is using iojs instead of nodejs's existing version scheme, which is interesting too. I just began a php device-configuration-management project and was strongly persuaded by a senior php developer that I should use nodejs instead, as he thinks nodejs _is_ the future and many big guns are using it for real deployment(netflix, linkedin,paypal...), just in time to try the fresh nodejs release for the new project.

dragonwriter 11y ago
> the new version number is using iojs instead of nodejs's existing version scheme, which is interesting too. Well, its a follow-on to both pre-merge iojs and pre-merge nodejs, and has breaking changes to both, so the most SEMVER consistent version number is the first major version greater than the greater of pre-merge iojs's last version number and pre-merge node's last version number -- which is exactly what they chose.