> GC makes everything much simpler up until it doesn't, and then it makes it much more complicated
I would say that's true in general, but in Go there's a lot more room to ask the GC to get out of your way if you need that than most.
I would say that's true in general, but in Go there's a lot more room to ask the GC to get out of your way if you need that than most.
Given the GP's note about the connection between written and compiled code and how a GC affects that, I think this is exactly what is being referred to. I.e. a GC makes everything much simpler up until it doesn't, and then it makes it much more complicated. That point may never be reached in many programs, but it may be hard in some cases to tell whether it's something you have to worry about at all.