Grandparent is 100% correct. Not sure why you brought up games to defend GC... we are the worst possible scenario for GC, barring the space shuttle. On my rece

Grandparent is 100% correct. Not sure why you brought up games to defend GC... we are the worst possible scenario for GC, barring the space shuttle. On my recently shipped C# game, I spent a ton of time writing custom memory management and tracking down memory leaks. Then I hired a coder with a background in web development, and it played out exactly like the grandparent comment described. Guy had Linq queries everywhere generating 4 MB of garbage per frame, because he just didn't know. The point is, we have to think about memory no matter what. So why bother with GC? It just makes it harder to control.