If you're not a Go programmer, bear this in mind: the Go compiler got noticeably slower after 1.4, but it is still extraordinarily fast; "run debounced after every keystroke" fast; "rebuild the world on a whim" fast.<p>Personally, I think the Go community is a little unhealthily obsessed with this particular metric.
There's something vicariously gratifying about posts like this. Optimization is some of the most fun programming to do: you have a crystal clear objective goal to go for and once you've got a profiler set up it's just:<p>1. Find slow thing.<p>2. Make faster.<p>3. See benchmark improve.<p>Some of the most satisfying coding I've done has been optimization.
You can find interesting details to this post in this thread:<p><a href="https://groups.google.com/forum/#!topic/golang-dev/DpMyPbclI3o" rel="nofollow">https://groups.google.com/forum/#!topic/golang-dev/DpMyPbclI...</a>
I'm confused how Go can be paraded as a low level systems language, which improves performance via concurrency, and yet the graph says it's compiler is still over twice as slow as when it was written in C?
The only thing preventing me from using Go on Windows is lack of production quality cgo on Windows x86 and x64.<p>For example, using external linking should "just work" with recent versions of sqlite3 but it fails on Windows.