Go 2, here we come

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 ]