I have written some pretty large, piggy programs in my day, but never until now did I write a program that does virtually nothing, and consumes 50 megabytes doing it. As soon as I press a button that makes the program do something, it jumps the size up to 60 megabytes.
This marvel of consuming memory is the output of Visual Studio 2005 WinForms. Usually I write programs that might use 2 or 3 megabytes until creating a huge number of image arrays or whatever that then jump the size up to maybe 30-40 megabytes. But the purpose of the program is to search through huge amounts of data, using the images in memory repeatedly in the algorithms.
I have a feeling that the Visual Studio 2005 "Common Language" stuff makes for very inefficient programming. This makes memory and disk makers happy, of course. But it somehow just seems plain old piggish to me.
I think of Microsoft products as the gigantosauruses of modern times.
This marvel of consuming memory is the output of Visual Studio 2005 WinForms. Usually I write programs that might use 2 or 3 megabytes until creating a huge number of image arrays or whatever that then jump the size up to maybe 30-40 megabytes. But the purpose of the program is to search through huge amounts of data, using the images in memory repeatedly in the algorithms.
I have a feeling that the Visual Studio 2005 "Common Language" stuff makes for very inefficient programming. This makes memory and disk makers happy, of course. But it somehow just seems plain old piggish to me.
I think of Microsoft products as the gigantosauruses of modern times.
No comments:
Post a Comment