Re:Backward Compatibility, Go 1.21, and Go 2
by mrweasel on Monday August 14, 2023 @01:00PM
(#37123442)
I did not know that was the reasoning or logic behind the Java 8, 9, 10 ... numbering, that clears up so many thing.
[ Parent
| on HN ]
Also relevant is that Sun had pulled the same trick with Solaris a few years earlier - Solaris 2.6 was followed by Solaris 7. Bigger version numbers make for better marketing. I am skeptical that backwards compatibility was strongly involved.
Apple also did a similar thing with OSX/macOS a few years ago - instead of making everything 10.XX they bump the major version (first number) every year now, continuing on from the 10 that the X represented, as if each version is the same increment as the jump from Mac OS 9 to Mac OS X (which was a jump to an entirely new codebase)
Android did that too, much earlier starting with 5.0. Previously the major version was something of an indicator of a major visual/conceptual redesign. 3.0 was the tablet version, 4.0 was the move to the holo design language, 5.0 was material. Then they just kept bumping the major version every year since.
I also assume it's just for marketing reasons.
Re:Backward Compatibility, Go 1.21, and Go 2
by chipotle_coyote on Monday August 14, 2023 @02:01PM
(#37124330)
I’d argue that the “everything is 10.x” for Mac OS was also basically marketing. :)