[nulltype]

I agree that this doesn't seem to actually cover practical memory management. In Go (and perhaps most languages) this seems to mean avoid allocations, and if you have to allocate, avoid the heap.

Maybe some information about how heap size and mutation rate affect GC would be interesting, as well as the future of the Go GC.

One interesting thing about Go is that if your objects contain no pointers, the Go GC does not have to scan them. So you can supposedly create huge slices of any type containing no pointers and the GC will have a much lower load on it.

There's a really good article from Dmitry Vyukov including memory related stuff here: https://software.intel.com/en-us/blogs/2014/05/10/debugging-...