2 ms·
No, I'm talking about a normal incremental build (which usually touch many things—I don't usually get to only recompile a single unit). If the planets align, I
by arghwhat 9y ago
No, I'm talking about a normal incremental build (which usually touch many things—I don't usually get to only recompile a single unit). If the planets align, I can get an incremental build to take just 30 seconds or so, but that's rare enough that I might mark such an event in my calendar. And that's on a beast of a server.
With Go, on my laptop, 30 seconds is the time it takes to perform a complete, optimized build of a medium-sized application, all dependencies and the standard library from source.
It's always so... frustrating whenever I go from a Go project back to our large C/C++ mixed codebase...
- notriddle 9y agoBecause Go doesn't do very much optimization. They've been fighting back performance regressions every time they try to improve the performance of the resulting binaries. https://dave.cheney.net/2016/11/19/go-1-8-toolchain-improvements https://dave.cheney.net/2016/11/19/go-1-8-toolchain-improvem...
- arghwhat 9y agoNeither does clang, gcc or rustc unless you explicitly tell it to. I was talking about a normal development session. Why would I make compilation time worse by making optimized builds?