GVM VS gox

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.

I'd recommend using something like gvm: https://github.com/moovweb/gvm

Ah neat. For ref: https://github.com/moovweb/gvm. Not sure how I never saw that one. I guess I just probably googled "update golang bash github" at some point a few years ago and went with it.

I use the Go Version Manager. It is really easy to use and you can manage as many versions as you want: https://github.com/moovweb/gvm

Checkout out official GVM repo for more here.

We can use the gvm Go version manager to use versioned installation which is a tool that provides an interface to manage Go versions.

I've been using gvm for a while now to manage my Go versions. It's absolutely amazing, however, it's always lacked the ability to automatically create Go installations per repo like RVM does with .ruby_version.

what's new/different from all others Go version managers like https://github.com/moovweb/gvm for instance ?

One of the biggest selling points for me when I started to use Go is cross compilation; I develop on a Mac, but run a lot of my code on a Linux EC2 instance (or been doing dev work on a Windows+WSL machine) and Go's cross compilation options (either via the built in tool or via something like gox are braindead easy. Rust's cross compilation however makes me want to drive my head thru my monitor... there are no easy ways to build a binary for Linux, Windows, AND Mac without having to dip my toes into CI services and with that comes an expense that for a hobby dev I'd prefer to not incur. Is there a brighter future for easy cross compilation with Rust?