Re: Garbage Collection - The Trash Begins To Pile Up
Andreas Huber wrote:
Ok, I'll bite. How does GC not relieve you from "memory management", at
least some of it? Note that I'm not saying "resource management",
because it is well known that GC (as implemented in .NET & Java) cannot
relieve anyone from that.
Memory is not infinite. I will repeat what Microsoft wrote about their
own language/framework:
You must understand, this is not some C++ lover/C# basher writing this.
This is Microsoft writing about a language/framework for which they
had 100% control over the design.
"Uncovering and correcting memory issues in managed applications can be
difficult. "
I laugh a small bit each time I read this sentence. First, one of the
biggest selling points of managed applications was GC. The other
selling point, which was probably one of greatest marketing drugs in
the 20th Century was "managed", giving the idea that it is somehow
better than "unmanaged". So here we have that memory, managed, and
difficult, are all be used in the same sentence, being written by the
very organization that claimed to make these things not difficult.
See again the problems:
* An OutOfMemoryException is thrown.
* The process is using too much memory for no obvious reason that
you can determine.
* It appears that garbage collection is not cleaning up objects
fast enough.
* The managed heap is overly fragmented.
* The application is excessively using the CPU.
Any engineer who designs a program that contains these problems in such
significant quantities as to warrant an article being written about it
should be ashamed of him/herself.
-Le Chaud Lapin-
Reference:
http://msdn.microsoft.com/msdnmag/issues/06/11/CLRInsideOut/default.aspx
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]