The official installation instructions for Go are available here.
For demonstration purposes we will show the installation procedure for OSX using Homebrew.
The process of installation is very easy. First, what you have to do is to run this command to install homebrew. It has a dependency on Xcode so you should ensure this is installed first.
Then you run the following to install homebrew:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
At this point you can now install Go with:
brew install go
You should follow any instructions recommended by your package manager. Note these may be host os specific.
You can verify the installation with:
$ go versiongo version go1.14 darwin/amd64
Go is opinionated.
By convention, all Go code lives within a single workspace (folder). This workspace could be anywhere in your machine. If you don't specify, Go will assume
$HOME/go as the default workspace. The workspace is identified (and modified) by the environment variable GOPATH.
You should set the environment variable so that you can use it later in scripts, shells, etc.
.bash_profile to contain the following exports:
export GOPATH=$HOME/goexport PATH=$PATH:$GOPATH/bin
Note you should open a new shell to pickup these environment variables.
Go assumes that your workspace contains a specific directory structure.
Go places its files in three directories: All source code lives in src, package objects lives in pkg, and the compiled programs live in bin. You can create these directories as follows:
mkdir -p $GOPATH/src $GOPATH/pkg $GOPATH/bin
At this point you can
go get and the
src/package/bin will be installed correctly in the appropriate
Modules aim to solve problems related to dependency management, version selection and reproducible builds; they also enable users to run Go code outside of
Using Modules is pretty straightforward. Select any directory outside
GOPATH as the root of your project, and create a new module with the
go mod init command.
go.mod file will be generated, containing the module path, a Go version, and its dependency requirements, which are the other modules needed for a successful build.
<modulepath> is specified,
go mod init will try to guess the module path from the directory structure, but it can also be overrided, by supplying an argument.
mkdir my-projectcd my-projectgo mod init <modulepath>
go.mod file could look like this:
module cmdgo 1.14require (github.com/google/pprof v0.0.0-20190515194954-54271f7e092fgolang.org/x/arch v0.0.0-20190815191158-8a70ba74b3a1golang.org/x/tools v0.0.0-20190611154301-25a4f137592f)
The built-in documentation provides an overview of all available
go mod commands.
go help modgo help mod init
Editor preference is very individualistic, you may already have a preference that supports Go. If you don't you should consider an Editor such as Visual Studio Code, which has exceptional Go support.
You can install it using the following command:
brew cask install visual-studio-code
You can confirm VS Code installed correctly you can run the following in your shell.
VS Code is shipped with very little software enabled, you can enable new software by installing extensions. To add Go support you must install an extension, there are a variety available for VS Code, an exceptional one is Luke Hoban's package. This can be installed as follows:
code --install-extension golang.go
When you open a Go file for the first time in VS Code, it will indicate that the Analysis tools are missing, you should click the button to install these. The list of tools that gets installed (and used) by VS Code are available here.
A good option for debugging Go (that's integrated with VS Code) is Delve. This can be installed as follows:
go get -u github.com/go-delve/delve/cmd/dlv
For additional help configuring and running the Go debugger in VS Code, please reference the VS Code debugging documentation.
An improvement over the default linter can be configured using GolangCI-Lint.
This can be installed as follows:
brew install golangci/tap/golangci-lint
A big emphasis of this book is around the importance of refactoring.
Your tools can help you do bigger refactoring with confidence.
You should be familiar enough with your editor to perform the following with a simple key combination:
Extract/Inline variable. Being able to take magic values and give them a name lets you simplify your code quickly
Extract method/function. It is vital to be able to take a section of code and extract functions/methods
Rename. You should be able to confidently rename symbols across files.
go fmt. Go has an opinioned formatter called
go fmt. Your editor should be running this on every file save.
Run tests. It goes without saying that you should be able to do any of the above and then quickly re-run your tests to ensure your refactoring hasn't broken anything
In addition, to help you work with your code you should be able to:
View function signature - You should never be unsure how to call a function in Go. Your IDE should describe a function in terms of its documentation, its parameters and what it returns.
View function definition - If it's still not clear what a function does, you should be able to jump to the source code and try and figure it out yourself.
Find usages of a symbol - Being able to see the context of a function being called can help your decision process when refactoring.
Mastering your tools will help you concentrate on the code and reduce context switching.
At this point you should have Go installed, an editor available and some basic tooling in place. Go has a very large ecosystem of third party products. We have identified a few useful components here, for a more complete list see https://awesome-go.com.