[pcwalton]

> Writing Go code in a Python-like way is going to be less performant than if you run escape analysis every compile and make deliberate effort to stay on the stack.

The fact that people are doing this tedious optimization is strong evidence of the fact that Go needs a generational garbage collector with bump allocation in the nursery.

The JVM has a fast generational GC, and as a result you don't have to do this kind of optimization to get good allocation performance.