Re: Can Someone Change My Mind About .NET?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Olaf.Baeyens_at_skyscan.be
Date: 04/30/04 

Date: Fri, 30 Apr 2004 13:16:48 +0200

> I come from the world of C++ programming, and I'm used to writing programs
that
>are actually executed by the CPU, and that run with some semblance of
performance.
> I have taken the time to explore this .NET thing, and found that not only
do .NET
>applications run extremely s-l-o-w-l-y, but the various .NET languages
amount to nothing
> more than interpreted script languages. It is the common language
run-time that actually executes your implementation.
>
Tests with C# here suggests that we have almost the same speed of our MFC
programs.
The JIT compiler needs time to compile the interediate language into native
cpu code, and that explains why the .NET program starts up slower, but if
you create the program with .NET design phylisophy and not MFC like
phylisophy, then it should reach the same speeds.

> I deeply resent this move toward "managed" code, and I'm disappointed that
the new Avalon user
> interface system in Longhorn will use only .NET facilities. Is this an
indication that subsequent
> versions of Windows will allow ONLY interpreted applications?
>
The biggest advantage if .NET is that it will improve security issuses since
the security is integrated into the code.
An OS based on .NET code will be far less vunerable for the current types of
worms and virusses. And I think the rest of the world would prefer an little
bit more secure windows that crashes less than a incredible fast computer.

Also note that, .NET programs will run faster compared to conventional
executable in the future since the Windows core is beeing replaced by pure
.NET technology.
It is the transition between managed and unmanaged that takes lots of time.
So it explains why .NET programs now are still a little bit slower since the
Windows core is still unmanaged and .NET prigrams must go through that
transition every time. When Longhorn is out, it wil be reversed. .NET will
be faster than conventional executables now.

> Does anyone else share my feelings about this situation? Can anyone put
forth some reason that I should feel better about
> embracing .NET, when it is so alien to me?
>
I understand the you completely that itis very confusing learning to program
in a .NET way, but you have to trust all the people here that it is the way
to go for future operating systems and programming languages. But it has a
steep learning curve as the technology matures.

Relevant Pages

  • Re: Can Someone Change My Mind About .NET?
    ... > run-time that actually executes your implementation. ... > The biggest advantage if .NET is that it will improve security issuses ... > executable in the future since the Windows core is beeing replaced by pure ... > to go for future operating systems and programming languages. ...
    (microsoft.public.dotnet.general)
  • Re: performance Winxp vs Linux
    ... Re: 'low' CPU consumption ... A benchmark app we use executes in a given time on a new Win2K box. ... Long story short - Under XP, drivers from the motherboard driver CD had ...
    (comp.lang.tcl)
  • Re: GetCurrentProcessorNumber() for XP?
    ... building a one->one mapping of APIC ID to CPU number; ... instruction executes, ... executing the appropriate cpuid instruction, ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Comments for reverse idea
    ... the CPU just executes binary coded instructions in memory. ... theese recording analyzes, just print everything that has executed? ... I still work on my static code analyser which will create a flow-chart ...
    (alt.lang.asm)
  • Re: Uses for memory barriers
    ... ordering consistent with all the serieses of values. ... then they will see the stores in the same order. ... specifying an order for events that take place on more than one CPU, ... A similar example would show that any stores CPU 2 executes ...
    (Linux-Kernel)