Go is not predisposed to write terse code. This is a feature, built into the language design. And it's great when working with a team of people with a wide variety of skill levels, but it's explicitly not a code golf language.
I know plenty of Go libraries that do feel terse when using them (e.g., the stdlib to begin with). I know plenty of Go libraries that feel overcomplicated (but I think it's not a fault of the Go language, but of the library designers). To put two I have been using recently:
