GVM VS Go Metrics

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 ?

Hello! I'm not sure if anyone else out there has struggled with out of date data in the default exponential decay sampling method in the go-metrics library, but if you have I just open sourced a sliding window implementation that should help ease the pain. More details on the rationale in the README.

Second method of make app level changes to emit metrics, something sort of a metric library .But this takes considerable dev efforts and coverage of all errors is gradual but meaningful