Go 2, here we come

Re:Go 2, here we come by bryanlarsen on Thursday November 29, 2018 @12:32PM (#18561940)

For the first round they are testing the GO 2 selection process by applying it to proposed changes for 1.13, which limits it to non-breaking proposals. It won't get interesting until they start selecting breaking proposals.

[ Parent | on HN ]

Re:Go 2, here we come by stcredzero on Thursday November 29, 2018 @12:48PM (#18562084)

It won't get interesting until they start selecting breaking proposals.

From what I see in the past couple of decades in popular languages, is there really a justification for breaking changes, from the POV of project maintainers?

[ Parent | on HN ]

Re:Go 2, here we come by fgonzag on Thursday November 29, 2018 @05:16PM (#18564648)

.net 2.0 had breaking changes, and it was absolutely justified. The ecosystem would not be where it is now without it. (.net 2.0 introduced reified generics, and required a major overhaul of the internals, with quite a bit of breaking changes)

[ Parent | on HN ]

Re:Go 2, here we come by copperx on Thursday November 29, 2018 @01:37PM (#18562565)

That's a good question because they ostensibly do it to get more users aboard, but in most cases, the result is the opposite (e.g., the Python 2/3 disaster).

[ Parent | on HN ]

Re:Go 2, here we come by littlestymaar on Thursday November 29, 2018 @04:19PM (#18564112)

The Python 2/3 switch was indeed a disaster, but in term of user gained and lost not so much: the number of Python users skyrocketed since 2007 despite the breakage nightmare.

[ Parent | on HN ]

Re:Go 2, here we come by hhmc on Thursday November 29, 2018 @07:27PM (#18565539)

C++11 introduced breaking changes (https://stackoverflow.com/questions/6399615/what-breaking-ch...) but is widely regarded as a boon to the language.

[ Parent | on HN ]

Re:Go 2, here we come by stcredzero on Friday December 07, 2018 @06:29PM (#18632636)

Yes, but in large part, those changes were quite obscure, in comparison to things like how to define classes.

[ Parent | on HN ]

Re:Go 2, here we come by stcredzero on Thursday November 29, 2018 @01:49PM (#18562693)

I was actually thinking of the POV of people writing in the language, not the maintainers of the project which is the language. I guess my point is that those two groups of people have different incentives.

[ Parent | on HN ]

Re:Go 2, here we come by bryanlarsen on Friday November 30, 2018 @07:06AM (#18568483)

Rust 2018 has breaking changes, and their mechanism for dealing with it is incredible.

[ Parent | on HN ]