goenv VS g

What does this have that https://github.com/syndbg/goenv doesn't?

However this is still a neat script OP! I was looking for something like this when installing Go for the first time and was contemplating between goenv, gvm, and asdf before settling on brew.

There are Go version managers (like goenv) that let you install multiple versions of go without polluting global PATH/GOBIN/GOPATH.

I use GoEnv. I hate that I have to do it, but I have valid (if annoying) reasons. I'd rather just keep the most recent version installed.

https://github.com/syndbg/goenv is a shell implementation that uses a shim to make calls to go. drewgonzales360s version will symlink to whichever version of Go a user chooses.

I am surprised I only saw one comment for goenv. This is literally the easiest way for all languages that have something similar (Python, Ruby, Go, Terraform, etc.). You need to uninstall all your go binaries, then install goenv, and all you have to do is to put in a project a .go-version file containing a single line with the version you need. The files are searched by the tool in a hierarchical order: if in the current directory where go is ran, no .go-version file is found, the tool will look up one directory, if there’s no ../.go-version will try again and so on. Let’s say in the end you will want to run the same go-version across all your projects, all you have to do is to find the first common parent directory and put a .go-version file in there, or simply just put a file in the root directory (/.go-version) or just use the global file (~/.goenv/version).

Not really answering your question but if you want to use Go 1.18 already there's a Go versions management tool called goenv that already has Go 1.18 and you can use already.

Kubebuilder doesn’t support Go 1.17, so we need to install Go 1.16. I decided to use goenv to manager Go versions.

i use goenv. works like a charm.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

I really like g: https://github.com/stefanmaric/g It’s simple, fast to use, and reliable.

If you are using a Unix based system you can use: https://github.com/stefanmaric/g I use it daily and works like charm, I only had some problems using `godoc` but it is solveble if you set the GOPATH to the go location and not the g installation directory

Don't use Brew for Go! Brew is great for a lot of things but but not for Go installation. So far this is the best Go version manager i've found. It can be nice to have different versions easily available. https://github.com/stefanmaric/g

I used this, easy and stable https://github.com/stefanmaric/g

Whatever the language, I find that using a version manager reduces stress considerably. This is the one I use, but there are others: https://github.com/stefanmaric/g