The Research Problems of Implementing Go
talks.golang.org
talks.golang.org
The framing of the tradeoffs (slow programmer, slow compiler or slow execution) is interesting. To me it suggests that we'll go with "slow compiler", because slow programmer is always expensive, and slow execution is expensive when run at Google scale.
Although they did stick "and bloated binaries" alongside "slow compiler", which says maybe they haven't quite made their mind up.
I agree though, I believe it should be possible to get good compilation speed with generic methods, leveraging the simplified syntax etc of Go.
[1] http://www.drdobbs.com/cpp/c-compilation-speed/228701711
No, you don't have to pick between "slow programmers, slow compilers and bloated binaries, or slow execution". people have been telling them that since what ... 5 years?
If it's got to be a slideshow, I much prefer this to SlideShare!