To read all comments associated with this story, please click here.
Bloat in the CLR? How much code do you think a JIT compiler and GC system take? Keep in mind that executable code rarely takes that much memory space in a program. Most of it is used for data structures and the program data itself.
Load time IS affected by having more code, since dynamic libs may get loaded and touched in many places before the OS decides that some things can be swapped back to disk. (I'd love to see a comparison article between Windows and Linux memory management and swapping).
GC is generally performance-neutral because it makes allocations and frees pretty fast (it's just a matter of moving a pointer for allocation and queuing a destructor for freeing), but it hits you at unexpected times with memory sweeps. Non-deterministic GC isn't great for situations where you want consistent low-latency.






Member since:
2005-07-22
"and to that guy above who has been modded down for trolling about KDE and C++, if you did ANY research you would know that Mono/.NET apps are compiled into binary code before running and NOT interpreted like Java is before the JiT compiler kicks in."
Aren't .NET apps compiled to CIL and interpreted by the virtual machine? How is that faster than a real processor? Even if they were compiled to native, I guarantee you that there's a lot of bloat in the CLR to make your .NET application faster than any other C++ equivalent, and would have a big memory footprint too.