John Timney ( MVP ) wrote:
The resulting exeecutables are not as fast as native C or C++ (if you
know how to write C/++ of course) but its a very fast language to
pick up and run with, thus it has many advantages over coding in C++.
Done any comparisons? Try it, you might be surprised.
I did some comparisons and was surprised and showed them to someone on
the C++ team and he told me that they were just what he expected.
The problem is that when most people think of .NET they think
'interpreter', or 'Java', or godforbid, Visual Basic. And so they think
'bad performance'. They shouldn't.
I think of the JIT compiler as being the back end of a C++ compiler (it
was written by people from the C++ team). If you discount the time that
the JIT compiler takes then for fully trusted code there is no reason
why it should be significantly slower than code generated by the
unmanaged C++ compiler. The only possible issue may be garbage
collection.
Of course, if you know of other areas of the .NET runtime which are
significantly slower than the equivalent in Win32 then you should post
them here so that we all can avoid using them <g>.
Richard
--
http://www.grimes.demon.co.uk/workshops/fusionWS.htm http://www.grimes.demon.co.uk/workshops/securityWS.htm