News for hackers. Stuff that matters.
Re:Backward Compatibility, Go 1.21, and Go 2 by ainar-g on Monday August 14, 2023 @01:00PM (#37123440)
> I wonder: why not go further and say "there will never be a Go 2" in order to eliminate ambiguity about this?

They did, five years ago. Albeit with an “if”.

https://github.com/golang/proposal/blob/d661ed19a203000b7c54...

> If the above process works as planned, then in an important sense there never will be a Go 2. Or, to put it a different way, we will slowly transition to new language and library features. We could at any point during the transition decide that now we are Go 2, which might be good marketing. Or we could just skip it (there has never been a C 2.0, why have a Go 2.0?).

> Popular languages like C, C++, and Java never have a version 2. In effect, they are always at version 1.N, although they use different names for that state. I believe that we should emulate them. In truth, a Go 2 in the full sense of the word, in the sense of an incompatible new version of the language or core libraries, would not be a good option for our users. A real Go 2 would, perhaps unsurprisingly, be harmful.

Re:Backward Compatibility, Go 1.21, and Go 2 by tmpz22 on Monday August 14, 2023 @01:42PM (#37124047)
> We could at any point during the transition decide that now we are Go 2, which might be good marketing.

Among the (entirely?) dev-oriented consumers of Golang would the shininess of "2.0" really outweigh the "ugh documentation is going to get harder to find" and "ugh I now need to increase my auditing of dependencies" and other similar fatigue?

Is Google universally good at marketing?

Re:Backward Compatibility, Go 1.21, and Go 2 by ilyt on Monday August 14, 2023 @06:52PM (#37127791)
But Java absolutely had versions that broke old code
Re:Backward Compatibility, Go 1.21, and Go 2 by pjmlp on Tuesday August 15, 2023 @03:11AM (#37131119)
> Popular languages like C, C++, and Java never have a version 2.

Only someone that never used those languages would state that, all of them have had breaking changes.

Re:Backward Compatibility, Go 1.21, and Go 2 by Thedarkb on Wednesday August 16, 2023 @05:58AM (#37144848)
C had a breaking change this year, pre-ANSI C programs need to have all of their function definitions changed for them to be compatible with C23.