Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I will just note that improvements to the GC and scheduler and other compiler optimizations are already implemented and will be part of Go 1.1

Also, the Go stdlib is very rich and covers lots of stuff, I have rarely found need for bindings to C libs unless it is OpenGL.

Which brings me to the point of games, there are already a couple of games using Go, the GC pauses are not as big of an issue because the GC is good enough (it is parallel) and in Go is easy to avoid generating garbage.



Questions for those more versed in Go's GC than I:

1) Let's say you want to do everything you can to avoid generating garbage. What would some those techniques be?

2) There is no delete function is there (for memory deallocation, not hashmap key removal)?

3) Is it possible to eliminate all garbage, and if so could you prevent the GC from starting up at all?

Possible existing answers that are a bit above my understanding (C# and Python spoil me):

http://news.ycombinator.com/item?id=4231048

http://blog.golang.org/2011/06/profiling-go-programs.html

https://groups.google.com/forum/?hl=fr&fromgroups#!topic...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: