News for hackers. Stuff that matters.
Re:Introduction to Go 1.1 by fulafel on Tuesday March 26, 2013 @06:02AM (#5442170)
On the go-nuts list people have been reporting large slowdowns with the new precise GC, and someone even backported the old GC to Go 1.1.
Re:Introduction to Go 1.1 by Raphael_Amiard on Tuesday March 26, 2013 @06:08AM (#5442182)
> with the new precise GC

The new GC is still not a precise GC, it's still conservative and non-tracing, just "more precise" (probably means they refined their heuristics) so you should probably not call it a precise GC.

Re:Introduction to Go 1.1 by asb on Tuesday March 26, 2013 @09:35AM (#5443106)
I thought Go 1.1 featured precise GC on the heap and conservative on the stack. Is that incorrect?
Re:Introduction to Go 1.1 by coldtea on Tuesday March 26, 2013 @06:31AM (#5442249)
So much for the GC that would improve on the old one...

Google could spend some cash to get them a real GC expert to work with the Go team, like they did for JS.