Yes, C++ build times were a significant factor in Go's creation. Rob Pike describes it here:
https://talks.golang.org/2012/splash.article
He covers all the same points about header files and how Go addresses those issues.
https://talks.golang.org/2012/splash.article
He covers all the same points about header files and how Go addresses those issues.
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.