But the solutions don't offer much over "go get", what would be the point to use them?
The Golang ecosystem is in an incredibly weak state when you compare it with other modern languages.
Major issues:
-)
Due to the lack of a proper package system, there's also no central pkg repository, which really hurts discoverabilty and growth of the ecosystem a lot. Just compare it to solutions like NPM for node, https://crates.io for Rust, Hackage for Haskell, etc...
Github + https://godoc.org/ is not a replacement for a proper package repository.
-)
Like I mentioned, way, way too many Go packages don't follow a proper release process with versioning and release notes. AT ALL. You often need to mirror repos for your own project, and closely track what upstream projects are doing. git clone + go get for your big projects just doesn't work.
This is incredibly problematic when developing big projects. A proper pkg solution should enforce versioning and release best practices.
Just the docs for the tip of master are far from what people expect.
"Serving 28 versions of 12 nuts published by 80 registered users."
There's just very little adoption for these, and there won't be unless it's official.
It seems to me that while I'm on the GitHub page anyway, it's reasonably convenient to just copy-paste the URL in a file so I can pull in the package and use it. I can't imagine just using a package repo for discovering new packages, that would be tantamount to just pulling whatever random code someone wrote that looks like it might solve my problem.