News for hackers. Stuff that matters.
Re:Go Escape Analysis Flaws by pron on Thursday February 12, 2015 @06:27PM (#9042040)
> Garbage never generated is garbage never collected.

But garbage that dies young is also garbage that is never collected, and that is the only kind of garbage EA can help with. Objects that die young are very cheap.

> Large enterprise Java apps often still have GC issues despite very advanced GCs to choose from

Very true, but never in the young generation.

Re:Go Escape Analysis Flaws by skybrian on Thursday February 12, 2015 @08:37PM (#9042410)
But how do you know it's in the young generation? A long-running thread or goroutine can outlive the young generation and then its heap-allocated objects will need to be moved. Stack allocation is more predictable.
Re:Go Escape Analysis Flaws by pron on Thursday February 12, 2015 @09:25PM (#9042557)
> Stack allocation is more predictable.

It is. It's just that I recall reading that the difference didn't turn out to be dramatic in practice. The object belonging to the bottom of the stack are promoted (they can't amount to much if they're stack-allocated, because your stacks aren't big anyway), and the reset is young. Whatever is mid-lived probably explains most of the non-dramatic difference (as well as young collections which are very cheap but not entirely free).