> There is no convincing reason I've seen for Go not to have a generational GC Well, they explored generational GC (after admitting that their uber-ultimate GC

> There is no convincing reason I've seen for Go not to have a generational GC Well, they explored generational GC (after admitting that their uber-ultimate GC that they marketed as future-proof until 2025 could be better): https://blog.golang.org/ismmkeynote https://blog.golang.org/ismmkeynote > It isn't that the generational hypothesis isn't true for Go, it's just that the young objects live and die young on the stack. The result is that generational collection is much less effective than you might find in other managed runtime languages.