Those are many of the same reasons I program in Go.

To add another:

* Go's build tools and the language's overall approach to building projects are fantastic.

For the vast majority of projects you don't need an external build manager like make. One of my least favorite bits of programming in C and C++, even when I was doing that on a daily basis years ago, was the huge morass of make/autoconf hell that would grow up around projects and would be very difficult to understand and reason about unless you were there for the entire project's development.

With Go open source projects (on git, svn, mercurial) much of the time you can just

  go get http://hosted-code-site/blah/(package)
  cd (package)
  go build

... out pops a working executable.