Hacker News Reader

You keep asserting that this $GOPATH is "braindead" but you provide no meaningful criticism of it or suggest any better alternatives.

I haven't messed with Go, but nothing about the idea of defining a path for source modules sounds braindead on its face to me. I certainly would give the benefit of any doubt to the designers of Go over some random troll.

View on HN

These are not source modules I'm talking about. If it was only necessary to set $GOPATH to point to source modules then everything would be fine. The problem is that go requires that $GOPATH points to a project's source tree to be able to build it, if the project is organized to store other go source files in subdirectories. We aren't talking about packages or modules intended to be reused in other programs. We are talking about how source code trees are organized.

The problem is that go requires that $GOPATH points to a project's source tree to be able to build it

How is that different than the /I ${INCLUDE} path of C/C++ compilers (and many other languages)?

Reply on news.ycombinator.com