Go does not need a Java-style GC
This is mostly stupid. Being able to have many GCs is a good thing. The big reason for &quot;value types&quot; is controlling spacial locality in memory, not GCs being bad per-se.<p>Also, they undersell the java&#x2F;c# situation. C# has &quot;ref, out, or in&quot;, but even without those, you can always make a reference wrapper that has the value type as a field. So &quot;reference types suck because coppying&quot; is nonsense garbage.