Hacker News Reader

I'm curious: what is it you don't like about importing packages in Go? With go get and goimports editor integration, I find third-party package integration pretty easy.

If it's a question of versioning or package.json-style dependency management, I agree that Go still has some significant pain points that haven't been fully addressed directly.

View on HN

Not the GP, but I note it's difficult to, say, take some code which uses package xyz and substitute the source-compatible package abc without editing every file. e.g. Try compiling a large project with a custom version of 'os' swapped in. (e.g. To add tracing, or simulate random I/O failures.)

Some package management systems can decouple what packages are called inside the code from what they're called outside.

Reply on news.ycombinator.com