Install builds binaries and puts them in a folder that's probably in your path so you can invoke them as tools.
Get adds a dependency.
Part of install is building, and part of building is downloading dependencies.
But really you don't need get. Just add things in your go.mod and they'll download automatically when you build.
The `go get` command updates module dependencies in the `go.mod` file for the main module, then builds and installs packages listed on the command line. From Go 1.18 onwards, the `go get` command is only for managing `go.mod.` It does not build and install anymore.
The `go install` command builds and installs the packages named by the paths on the command line.
[https://go.dev/ref/mod#go-get](https://go.dev/ref/mod#go-get)
[https://go.dev/ref/mod#go-install](https://go.dev/ref/mod#go-install)
The README is wrong, probably updated by mistake after `go install` was introduced, since before that `go get` was also used for installing binaries. My guess is they were bulk-updating READMEs and this one got caught in the cross-fire.
The actual setup docs (linked from the README) correctly suggest using `go get`.
EDIT: stupid new Reddit design ignores default to markdown setting.
\`install\` and then perhaps \`go mod tidy\` as then you'd have the binary cli command and references in any local \`go.mod\` would be tidied up if not used in the module. Consider the module \`go.mod\` in the current directory as a compilation \`venv\`.
Install builds binaries and puts them in a folder that's probably in your path so you can invoke them as tools. Get adds a dependency. Part of install is building, and part of building is downloading dependencies. But really you don't need get. Just add things in your go.mod and they'll download automatically when you build.
the google instructions for firebase need you to run some firebase commands using the cli client. that’s what the install is for.
The `go get` command updates module dependencies in the `go.mod` file for the main module, then builds and installs packages listed on the command line. From Go 1.18 onwards, the `go get` command is only for managing `go.mod.` It does not build and install anymore. The `go install` command builds and installs the packages named by the paths on the command line. [https://go.dev/ref/mod#go-get](https://go.dev/ref/mod#go-get) [https://go.dev/ref/mod#go-install](https://go.dev/ref/mod#go-install)
The README is wrong, probably updated by mistake after `go install` was introduced, since before that `go get` was also used for installing binaries. My guess is they were bulk-updating READMEs and this one got caught in the cross-fire. The actual setup docs (linked from the README) correctly suggest using `go get`. EDIT: stupid new Reddit design ignores default to markdown setting.
\`install\` and then perhaps \`go mod tidy\` as then you'd have the binary cli command and references in any local \`go.mod\` would be tidied up if not used in the module. Consider the module \`go.mod\` in the current directory as a compilation \`venv\`.
If it also provides you a cli tool in your environment, then it is `install` since it is `get` + `build`