[kid0m4n]

Actually, looking deeply at Go from a performance perspective (as I have been, the last couple of days) has revealed a bunch of low hanging fruits/missed optimization opportunities in the Go compiler. That was 50 % the intent of the grand father blog post

[packetslave]

Sure, there's plenty of work still to be done. Go 1.0 is only 18 months old, with 1.1 only 6 months old.

C++ has 30 years of history behind it, MS VC++ is 20 years old, Intel's C++ compiler is at least 10 years old, etc.