well now it leans in to go's reproducible tooling so it's declaratively configured and shared between your team and your CI/CD environment too.
There are many tools that arent written in golang, and therefore not manageable via this approach. I don’t really understand why I would use this.
The `go tool` stuff has always seemed like a junior engineering hack — literally the wrong tool for the job, yeah sure it gets it working, but other than that it's gross.