News for hackers. Stuff that matters.
Re:Visual Studio 2017 Release Candidate by gregmac on Wednesday November 16, 2016 @01:43PM (#12969998)
I am beginning to think that Microsoft's bad verison naming is entirely on-purpose.

Windows has had terrible naming since NT -- back and forth between names/numbers/years (or nonsense like "Anniversary Update" or "R2"), have a completely different scheme for Server vs Desktop, and if you look at the corresponding kernel versions of these releases[0], the major/minor bump in versions seems completely arbitrary.

.NET is even worse. Framework vs CLR is a mess [1]. Core started over at 1.0. .NET Standard brings some consistency to it all, but also introduces another versioning scheme with overlapping numbers that mean different things[2].

But even other divisions do this: Xbox -> Xbox 360 -> Xbox One.

[0] https://en.wikipedia.org/wiki/Windows_NT#Releases

[1] https://en.wikipedia.org/wiki/.NET_Framework_version_history...

[2] https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introduci...

Re:Visual Studio 2017 Release Candidate by Pharylon on Wednesday November 16, 2016 @02:17PM (#12970408)
You forgot about Windows 9. ;)
Re:Visual Studio 2017 Release Candidate by ZenoArrow on Wednesday November 16, 2016 @02:23PM (#12970462)
Was meant to have been skipped because it was too similar to Windows 9x (Win95, etc...).
Re:Visual Studio 2017 Release Candidate by gregmac on Wednesday November 16, 2016 @02:53PM (#12970810)
Which wouldn't have been a problem if they followed a consistent naming convention in the first place...
Re:Visual Studio 2017 Release Candidate by collinmanderson on Friday November 18, 2016 @11:15AM (#12987757)
Windows 2000 = 5 Windows XP = 5.1 Windows Vista = 6.0 Windows 7 = 6.1 Windows 8 = 6.2 Finally, they have Windows 10 == 10
Re:Visual Studio 2017 Release Candidate by bung on Wednesday November 16, 2016 @07:07PM (#12972907)
On purpose... but any guess as to why?