> I don't think it's simple. I mean, it kinda is. If you're a Go developer that went further than hello world, you will probably be aware of these two possibil

> I don't think it's simple. I mean, it kinda is. If you're a Go developer that went further than hello world, you will probably be aware of these two possibilities: If . contains a "main" package then it's "go run .", otherwise the source for the binaries probably reside in "./cmd/X" and you have to run "go run cmd/X". You can probably find Go projects that don't follow these rules, but I doubt anyone would want to interact with them.