News for hackers. Stuff that matters.
Re:Switching from pyenv, rbenv, goenv and nvm to asdf by tptacek on Tuesday April 05, 2022 @02:45PM (#30923154)
I get pyenv and rbenv. I do not get why anyone would use goenv. I'm sure there's some corner-casey reason, but it's not a mainstream thing. I can't imagine working in Ruby or Python without wrappers, but Go, just keep the most recent version installed and that's pretty much it. If you're new to Go and installing something like goenv because you had to do that for all the other languages... reconsider!
Re:Switching from pyenv, rbenv, goenv and nvm to asdf by ryanschneider on Tuesday April 05, 2022 @04:53PM (#30924877)
I’m not sure if this is a feature or bug but `asdf` requires you to recompile every tool installed via `go install` (nee `go get`) when you change go versions.

IIRC the main reason our team started tracking go versions was we were already using `asdf` for tracking other tools and it’s a nice way to ensure that everyone/everything was using the same to version (e.g. for unit tests which usually aren’t run in a container) but it is another spot to keep in sync with the Dockerfile.

Re:Switching from pyenv, rbenv, goenv and nvm to asdf by EscargotCult on Tuesday April 05, 2022 @03:52PM (#30924087)
+1 the only thing that's "surprised" me between Go releases has been their changes to build flags in 1.18, and gofmt takes care of that anyway. Now that I think of it, gofmt changes if you have autoformatting enabled is probably the only "breaking" change that might happen between minor releases, but I haven't seen any issues with this from 1.15 through 1.18. In any case, if gofmt changes are disruptive enough to block upgrading, then a team has some deeper-seated issues in how they ship.