Hacker News Reader

I'm not talking about gc. I'm talking about go. You know, the program which is extensively marketed as the only program which is required to build and run Go programs, and the standard and default way to deal with Go, from installing third-party packages and running your program through an interpreter.

Referring to gc makes as much sense as referring to gccgo.

View on HN

Not sure if you know this (or anything about Go), but the go tool just uses a bunch of other programs to accomplish what it does (including git, bzr, the compiler and the linker).

If you want to do your own thing, you're free to ignore the rest of the community in this respect, and create your own build mechanism. In fact, if you pass the "-x" flag to the go tool, you can even see how its accomplishing what its accomplishing; which might help you write this better build tool.

What do you want? You don't want to use the `go` tool, DON'T USE IT. Seriously, the alternative that you are implying that you want is already available to you.

Reply on news.ycombinator.com