Re:Go 1.6 Release Candidate 1 is released
by thewhitetulip on Wednesday January 27, 2016 @11:33PM
(#10986305)
We can see the way Go solves this problem without breaking your code, a way not taken these days where not so well designed solutions break when we have to upgrade. Python 2 and python 3, angular 1 and angular 2.
I guess this is the difference between a pet project gone wild and a well thought and well designed programming language designed to make the process of building applications faster and better!
[ Parent
| on HN ]
Re:Go 1.6 Release Candidate 1 is released
by jzelinskie on Wednesday January 27, 2016 @11:57PM
(#10986383)
You are conflating major and minor versions of software. Python 2 & 3 and Angular 1 & 2 are major versions that have forward declared breaking changes. If/When Go 2 is released, it will contain language breaking changes.
Re:Go 1.6 Release Candidate 1 is released
by sriram_malhar on Thursday January 28, 2016 @07:54AM
(#10987840)
Go is too young, and has extremely small adoption compared to Python, C, C++, Java. When a language has been around for so long that entire idioms have changed (functional in, object out, reactive in, iteration out etc.), the usage landscape has changed (from desktop scripts up to cloud-scale and down to mobile-app scale), it is natural for the language to have to adapt.
The hope is that Go will have enough adoption to require breaking changes!