Not entirely. Go still doesn't have a generational collector so high allocation rates cause more GC's that must examine long-lived objects. As such, short-live

Not entirely. Go still doesn't have a generational collector so high allocation rates cause more GC's that must examine long-lived objects. As such, short-lived objects have little impact in Java (thank god for that!). They will have second order effects in Go.