News for hackers. Stuff that matters.
Re:Io.js v3.0.0 by barosl on Tuesday August 04, 2015 @07:20PM (#10006968)
It is worth noting that Windows also maintains an internal version that is only visible through the `winver` command (the NT version).

  Windows XP:    5.1
  Windows Vista: 6.0
  Windows 7:     6.1
  Windows 8:     6.2
  Windows 8.1:   6.3
  Windows 10:    10.0 <-- New!
Interestingly, they also bumped the internal version to 10.0 in Windows 10. It was actually 6.4 in the early preview releases, but soon became 10.0. I find it intriguing considering Microsoft's conservative notion on backward compatibility, but even Microsoft seems to have finally reached the point of refreshing a version number.
Re:Io.js v3.0.0 by chadzawistowski on Tuesday August 04, 2015 @08:58PM (#10007446)
In Windows 8.1, the GetVersion(Ex) APIs were deprecated. That means that while you can still call the APIs, if your app does not specifically target Windows 8.1, you will get Windows 8 versioning (6.2.0.0).

Microsoft didn't want to relive the hassle of Vista's major version bump. Thanks to the deprecation of the GetVersion APIs, however, programs will think they are on Windows 8 unless they explicitly opt-in to new version behavior. This meant Windows 10 could actually use the 10.0 version number without breaking stuff again.

Re:Io.js v3.0.0 by andreasklinger on Tuesday August 04, 2015 @08:18PM (#10007292)
> I find it intriguing considering Microsoft's conservative notion on backward compatibility, but even Microsoft seems to have finally reached the point of refreshing a version number.

Alternatively that bump could be caused by a request from a marketing manager