Go 1.17 is deprecating the traditional use of 'go get'

Re:Go 1.17 is deprecating the traditional use of 'go get' by jacquesm on Friday June 25, 2021 @01:31PM (#27633852)

This is an interesting side effect of open source. Companies can not afford to break their customers deployments and so tend to bend over backwards to guarantee backwards compatibility. But in open source that link is much more tenuous and project reputation does not directly translate into monetary value in most cases, especially if there is no commercial model attached to a particular solution.

This is made worse by the fact that open source is typically developed with a very early public release to drive adoption, rather than that the first decade or so the solution is battle tested in-house and only released when most of the kinks have been worked out.

[ Parent | on HN ]

Re:Go 1.17 is deprecating the traditional use of 'go get' by ferdowsi on Friday June 25, 2021 @01:37PM (#27633928)

Any type of backwards compatibility breakage provides a decision point to either decide:

* do I put in the work to upgrade all my code so that it works with this new version?

* do I jump ship to some other library/language that I've been interested in?

In the Python 3 breaking case, it provided good reason for engineers at major enterprises to start building in Go instead of investing in the Python 3 upgrade.

Another debacle was Angular being completely backwards incompatible, giving an opportunity for React to gain mindshare.

[ Parent | on HN ]