Linked by Thom Holwerda on Sun 23rd Jul 2006 21:48 UTC
Editorial Politicians. They are a certain type of people. I do not like them. Many do not like them. I think if there's one thing all of man has in common, whether he be Christian or Muslim, black or white, young or old, American or European, is a dislike of politicians. But then-- why on earth do we allow politics to complicate software? Note: Sunday Eve Column.
Thread beginning with comment 145634
To read all comments associated with this story, please click here.
RE[2]: Everybody's asking "Why not?"...
by sbenitezb on Mon 24th Jul 2006 03:33 UTC
sbenitezb
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.

PlatformAgnostic Member since:
2006-01-02

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.

Reply Parent Bookmark Score: 1

jmansion Member since:
2006-02-20

You *can* interpret CIL, but it was designed from the get-go to be JIT-compiled: arguably the JVM acquired JIT as an afterthought optimisation. The MS CLR doesn't have an interpreter: I believe mono does (mint?).

Shucks: lets just use Eiffel and be done. ;-)

Reply Parent Bookmark Score: 1