News for hackers. Stuff that matters.
Re:Compile Go programs 7x faster by lazyjones on Wednesday August 10, 2016 @07:33AM (#12260854)
This is basically a wrapper for 'go install'. See this post / linked blog posts for an explanation why this is faster/useful: https://twitter.com/davecheney/status/697171533215576064
Re:Compile Go programs 7x faster by jerf on Wednesday August 10, 2016 @09:09AM (#12261360)
After reading this discussion and the source of the project, I've flagged this. This "compile Go faster" project really is just about 5 lines of modestly useful bash, and even as someone who often complains people tend to overstate the uselessness of benchmarks, those benchmarks are truly useless. Along with being too small to measure anything useful, almost certainly being dominated by startup overhead, you can't benchmark two fundamentally different things like that. Incremental builds, regardless of language, are not "3x faster" or "9x faster", they're doing fundamentally less work. It's not quite correct to say they're in a different O() class, but that's at least the right sort of thought. O(n^2) algorithms aren't any number of "x" times faster than a O(n^3) algorithm, they're more fundamentally faster than that metric can capture; similarly here.

To the author, I'm not complaining that you have this on github per se, but you may want to make it more clear what's going on here if you're going to submit it to HN. For instance, this is one of those projects where you could literally inline the source into the README.md. And I'd drop the benchmarks, those really aren't useful. Or at least drop the "x times faster" column.

Re:Compile Go programs 7x faster by tptacek on Wednesday August 10, 2016 @11:13AM (#12262345)
You flagged _the story_, on HN? Don't do that. It's valuable if only as a hook for comments like yours.
Re:Compile Go programs 7x faster by jerf on Wednesday August 10, 2016 @11:20AM (#12262395)
The "it could create good comments" is not a good metric for not flagging something, because there is no link for which that is not true, or at least someone would argue for it.

While I again want to emphasize I'm not really being that critical of the author for creating it, because people are welcome to put whatever they want on github, it's a thin piece of content whose thin content is also somewhat misleading, that was upvoted to the top of HN. I'm still comfortable with this, barring the admin staff disagreeing with me.

Re:Compile Go programs 7x faster by tptacek on Wednesday August 10, 2016 @11:54AM (#12262666)
That's true for off-topic stories, which stories are the actual purpose of the flag button. It's not true for stories we simply disagree with. In this case, you happen to be right, but everyone has a bunch of topics they believe themselves to be right about.
Re:Compile Go programs 7x faster by shazow on Wednesday August 10, 2016 @11:15AM (#12262366)
The length of code of a program should not be a metric for how useful or valid it is.

This is a great shortcut for something that I've been doing manually for years and I'm happy to have stumbled on it and the surrounding discussion. Please don't flag stories like this.

Re:Compile Go programs 7x faster by nemild on Wednesday August 10, 2016 @09:57AM (#12261737)
I have to echo everything said by @jerf. One additional suggestion is to write a blog post highlighting ways to improve the workflow for go developers and help them to understand why certain things are better than others, as your work here slots in nicely.

You could also explain in detail what goes on behind the scenes in an incremental build.

Re:Compile Go programs 7x faster by nickcw on Wednesday August 10, 2016 @07:55AM (#12260956)
Yes, never use go build, always use go install!

go build builds everything, whereas go install does an incremental build on the stuff that has changed and installs it (either in GOPATH/bin or GOPATH/pkg).

Re:Compile Go programs 7x faster by ithkuil on Wednesday August 10, 2016 @09:43AM (#12261627)
FYI, there is also `go build -i`, which is behaves like `go build` in terms of what executable artefacts it produces and where it puts them (i.e. it doesn't install stuff in $GOPATH/bin) but preserves object files for all the dependent packages like `go install` does
Re:Compile Go programs 7x faster by jjnoakes on Wednesday August 10, 2016 @08:51AM (#12261248)
Why does "go build" build more than what is necessary for "go install"?

Shouldn't "go build" just do incremental builds and be faster across the board?

Re:Compile Go programs 7x faster by peterevans on Wednesday August 10, 2016 @08:58AM (#12261294)
Running `go build` is a lot like running `make clean` before you compile.
Re:Compile Go programs 7x faster by TheHippo on Wednesday August 10, 2016 @09:04AM (#12261323)
Just use `go build -i` to install everything and compile only packages that have changed.
Re:Compile Go programs 7x faster by fitzwatermellow on Wednesday August 10, 2016 @08:01AM (#12260994)
"all the go commands operate on packages, the use of files is a degenerate case only to support go run"

guilty. typing in "go run" for quick scripts is one hard to conquer habit ;)

Re:Compile Go programs 7x faster by jerf on Wednesday August 10, 2016 @08:29AM (#12261122)
For quick scripts I don't see how it's wrong. I mean, even wrong is really just "wasting time a bit" here.