So it seems this is v4 because io.js got to v3 in it's short lifetime. Is Chrome... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		stephenr on Sept 4, 2015 \| parent \| context \| favorite \| on: Node.js v4 Release Timeline So it seems this is v4 because io.js got to v3 in it's short lifetime. Is Chrome somehow setting the pace for version numbers? We don't have major.minor.path. Semver is pointless. A version is an integer, and every change is a new version? How long until we see Uint32 overflows on a version number?

saghul on Sept 4, 2015 [–]

io.js does follow semver, that's why it's at 3.x, because certain changes required the major version bump.

Node v4 will be the first Node to follow semver.

I get that you don't like Chrome style versioning, but that's not what's going on with Node.

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