> Go also doesn't have the problem of conflicting system level packages.

Sure, as long as you're not using CGO and dynamic linking. Otherwise you'll get the exact same problems as the others.

> Go doesn't have to deal with interpreter dependencies

As long as Go is forward compatible this will old true, but I don't think this was the point of the comment.

'go get' is a half-baked package manager and yes it fetch packages and resolve dependencies between packages so that's a package manager. It just doesn't care about versions. Other languages have solved the issue by requiring a third party tool, Ruby even has its own build tool.

There is a reason why some gophers are working on an actual package manager...