> the JVM's GC is generational, and it appears Go's GC is not. Correct, that's slated for the 1.6 timeframe: > While other goals may intervene, 1.6 will most

> the JVM's GC is generational, and it appears Go's GC is not. Correct, that's slated for the 1.6 timeframe: > While other goals may intervene, 1.6 will most likely be used to improve throughput by adding bump pointer allocation as well as a generational copy collector for nursery (new) spaces. The mature (old) space will be managed using our concurrent GC. Source: https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLovrHvvLhK_h0KN8woTO4/preview?sle=true https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLo...