Re:Go 1.17 is deprecating the traditional use of 'go get'
by bla3 on Friday June 25, 2021 @10:21AM
(#27631093)
Go spends a lot of effort on making sure the language is backwards compatible. Which is great! Weird they're so nonchalant about tooling changes.
[ Parent
| on HN ]
Re:Go 1.17 is deprecating the traditional use of 'go get'
by janslow on Friday June 25, 2021 @10:34AM
(#27631288)
In most cases, a breaking tooling change should only impact the root project (e.g., they need to change their readme from `go get` to `go install`), so there's only one codebase to fix and it's in the control of the person upgrading the tooling.
Whereas, a breaking language change could impact transitive dependencies of the root project, which a developer doesn't have control over.
Re:Go 1.17 is deprecating the traditional use of 'go get'
by throwaway894345 on Friday June 25, 2021 @10:55AM
(#27631562)
Moreover, breaking a language change can result in many changes over any given project including insidious bugs. Breaking the tooling behavior means you have to update your build script and your workflow. Meh.