Originally posted by Bob Ruth:
2) garbage collection demands it's price. It HAS to execute code to do it's job so, when it is time for it to run ( as in.... available heap space is getting low and you are needing more memory) it HAS to run and can impact the performance of your application.
You make it sound as though this cost is peculiar to GC. But explicitly freeing objects with or without destructors, takes time too. It's just that with a GC, it possible that it will happen in big chunks at some inopportune time, while explicit destruction uniformly slows everything down.