Linked by Eugenia Loli on Fri 7th Jul 2006 03:15 UTC
Thread beginning with comment 141158
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE[2]: One thing I don't understand
by n4cer on Fri 7th Jul 2006 20:22
in reply to "RE: One thing I don't understand"
However, as just a pure end user, I always, I mean always prefer an application that has been compiled to native machine code (C/C++), that is, when I'm aware of what the app was written in.
All .NET code is compiled to native machine code before execution. For max compatibility, compilation happens either at install or runtime (defaut). You can also pre-compile seperate binaries for each platform like in C/C++ by using NGen or similar tools.




Member since:
2005-07-12
I couldn't agree with you more.
What matters is the end user experience, not the convenience of garbage collection, or increased developer productivity, or "pure OOP" design, or whatever.
It seems that for corporate or internal apps, Java and .Net are kings. In this environment, users have to use what they're told to, whether they think the interface is slow and clunky or not. And the productivity gains received when using a garbage collected, managed language is a big win, and there is no loss in usage. For corporate, internal apps, the audience is captive.
But in commercial software, especially shrink wrapped software, C and C++ are kings, by a long margin. The same holds true for a lot of open source software. In this arena, the audience is not captive, and will not tolerate slow, clunky, memory hogging, sometimes alien looking applications. Here, the increased performance and less memory usage of the end product make it worthwhile, and indeed necessary, to sacrifice the programmer convenience and increased productivity of applications built on managed code.
And, even though I was singing the praises of Mono (and Java and .Net) in my previous post, that was from my developer perspective. Those are nice tools to work with.
However, as just a pure end user, I always, I mean always prefer an application that has been compiled to native machine code (C/C++), that is, when I'm aware of what the app was written in. In every case, a C/C++ app always out performs, and delivers a better overall user experience, and uses way less memory, then an equivelent Java/.Net app. There are no exceptions, not in my experience.
Edited 2006-07-07 19:44