3 ms·
In other ecosystems, I could see how this could be a problem, but I don’t think I’ve ever had a problem with a Go upgrade. What’re the actual, practical result
by cweagans 6mo ago
In other ecosystems, I could see how this could be a problem, but I don’t think I’ve ever had a problem with a Go upgrade.
What’re the actual, practical results of a package pushing you towards a higher go version that you wouldn’t otherwise have adopted right away? Why is this actually important to avoid beyond “don’t tell me what to do”?
- skybrian 6mo agoOne potential reason is that Go does drop support for older OSes sometimes. For example, Go 1.22 is the newest version that works with older Mac OSes. https://go.dev/doc/go1.22#darwin https://go.dev/doc/go1.22#darwin
- cweagans 6mo agoshrug maybe so. But then again, I can't say I'm too torn up about losing support for an EOL OS version.