3 ms·
Wasn't this one of the reasons why the Go project started at Google, not necessarily for Chrome, but because C++ project compile speeds were horrendous for some
by djhworld 9y ago
Wasn't this one of the reasons why the Go project started at Google, not necessarily for Chrome, but because C++ project compile speeds were horrendous for some internal projects.
Not saying Chrome could and should just switch to Go, it definitely would not be the right fit! But it's interesting that these sorts of builds still occur and consume a lot of developer's time.
- jdcarter 9y agoYes, C++ build times were a significant factor in Go's creation. Rob Pike describes it here: https://talks.golang.org/2012/splash.article https://talks.golang.org/2012/splash.article He covers all the same points about header files and how Go addresses those issues.