4 ms·
I want to try out Go, but the problems exposed by the garbage collector on 32bit systems scared me away. Is that still the case with the latest version 1.0.2 ?
by bad_user 14y ago
I want to try out Go, but the problems exposed by the garbage collector on 32bit systems scared me away.
Is that still the case with the latest version 1.0.2 ?
Also, is there any chance for a precise generational garbage collector to get implemented for Go? As far as I know, pointers make the implementation of precise garbage collectors difficult.
- jessemc 14y agoThere is code to make the garbage collector more precise currently in review. A few packages from the stdlib were changed to reduce the chance that package level variables might pin used sections of memory. Most people have no problems with the garbage collector on 32bit systems.
- akavel 14y agoAFAIK, yes it is still the case (although somewhat slightly improved), but precise collector is officially expected (and being worked on) for version 1.1 . The latter was explicitly said on a Q&A session on Google I/O conference, the video is available somewhere on teh interwebs. edit: I think it's this one: http://youtu.be/sln-gJaURzk http://youtu.be/sln-gJaURzk ("Meet the Go team"), but maybe some other from: http://blog.golang.org/2012/07/go-videos-from-google-io-2012.html http://blog.golang.org/2012/07/go-videos-from-google-io-2012... (sorry, don't have time to watch them all again now to make sure ;)
- bad_user 14y agoThat's good to know, thanks.
- jussij 14y ago> I want to try out Go, but the problems exposed by the garbage collector on 32bit systems scared me away. If you run a 64 bit server then these problems just goes away. And from all accounts these issues will also be fixed for 32 bit systems in then next Go release or two.
- jff 14y agoHere's a dime, go buy yourself an AMD64.