That's what makes it amusing, but I don't necessarily agree with "Go code that uses 20% of CPU time in GC is usually bad Go code", and I certainly would disagree if you omitted the word "usually".
Quality code is optimized based on what really matters, and I'm skeptical GC cycles really matter here.