"What remains to be seen, of course, is how all of this Go code will perform."
They're pretty clear and honest that Go's performance characteristics are an unknown and not the reason it was chosen.
They're pretty clear and honest that Go's performance characteristics are an unknown and not the reason it was chosen.
When talking about Java:
> JVM garbage collection is notoriously expensive.
> Java’s known performance issues made it unappealing.
> However, in our past experience, we ported a large system from Java to Go, which greatly decreased its memory footprint and garbage collection overhead.
When talking about Go:
> What remains to be seen, of course, is how all of this Go code will perform.
Yet: The JVM's GC is superior to Go's, Java tends to outperform Go, and a large memory footprint is a necessary evil for getting good performance out of any GC.