Go’s major versioning sucks – From a fanboy

Re:Go’s major versioning sucks – From a fanboy by dmitriid on Saturday March 05, 2022 @07:06AM (#30566788)

1. You build your project, and it fails in the places where API changed.

IDEs can even pinpoint those locations without building a project

2. You run tests and they fail if the behavior changed

Literally nowhere is "oh, do an automatic search/replace of imports" is a tool for fixing your project or figuring out necessary changes. Except in go, apparently.

[ Parent | on HN ]

Re:Go’s major versioning sucks – From a fanboy by paskozdilar on Saturday March 05, 2022 @11:59AM (#30569220)

Willingness to play russian roulette with major versions may work in small organizations. In large-scale, you can't risk subtle behavior change that still compiles. That's the source of many black magic debugging sessions.

[ Parent | on HN ]

Re:Go’s major versioning sucks – From a fanboy by dmitriid on Sunday March 06, 2022 @12:24AM (#30575257)

Grepping and replacing import paths isn't a good tool for finding subtle behavior changes. Especially in big projects.

[ Parent | on HN ]

Re:Go’s major versioning sucks – From a fanboy by paskozdilar on Sunday March 06, 2022 @05:43AM (#30576560)

Yeah, but checking each line of code that uses the import is. Especially in big projects.

[ Parent | on HN ]