Re: Is that a joke ?

The .Net framework DOES compile code into native op-codes. It is NOT an
interpreter.

While some operations run quicker in C++, including the initial load of the
app into memory, the fact is that .Net apps are not substantially slower,
when running, than C++ apps for most uses. Perhaps you have hit on a
situation that runs slower? Perhaps if you tell is a little more about your
app?

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Ted Nicols" <__NoSpAm__deltafox@xxxxxxxx> wrote in message
news:e3UQUWneFHA.3280@xxxxxxxxxxxxxxxxxxxxxxx
> That's what I keep asking myself whenever develop in .NET. Is this a joke
> a farse or just a bad dream?
>
> .NET is slow, actually slow is just a polite word I can use in a
> newsgroup.
>
>
>
> .NET is just a VM and as one it works very slowly, before and after JIT. I
> don't understand why some people insist that a VM can be compared with
> native code. I really feel sick, whenever compare native C++ code against
> the same code ported to C#. I don't know what is the performance loss with
> databases or corporate solutions but my math/CAE functions run times
> slower in .NET.
>
> Managed code might be fast enough for enterprise apps, database front ends
> or asp intranets. It probably looks fast to Java or VB developers but what
> about real time applications?
>
> What about CAD, CAE, CAM, scientific applications, utilities, math,
> imaging, desktop publishing etc. What should developers who write such
> applications must do ? Port them into UNIX ?
>
>
>
> What happened to the rule i knew twenty years ago? "Next version of
> anything should be at least faster and more stable than the previous one"
>
>
>
> I have many questions for MS developers, although I'm sure nobody will
> ever answer.
>
>
>
> 1. Is .NET just an approach to enterprise development?
>
> 2. Or another battle with Sun's Java
>
> 3. Or an MS conclusion that performance doesn't matter any more
>
> 4. If .NET was slow for WinFS, Office or Longhorn then why we have to
> believe that is fast for our own applications?
>
> 5. If Microsoft want a new API why that must be based on VM technology?
>
> 6. Why MS call .NET a "safe" framework, safe from what? Safe from hackers,
> I don't thin so, they can write anything they want in unmanaged code. Safe
> from mem leaks, a garbage collector doesn't make good programmers or safe
> applications. I still wonder what "safe" means.
>
> 7. Winforms1 will become obsolete because of WF2. WF2 will become obsolete
> because of Avalon. Then why they introduced them? Just to have something
> that hides Win32/GDI calls?
>
> 8. Longhorn drivers, kernel and anything "low-level" will be written in
> native code. LH must run in 64bit processors too, so native code must be
> natively compiled in 64bit API calls. That means Win32 will become Win64.
> Why MS don't simply implement WinFX as an OO frontend to Win32/64 API,
> leaving out the VM?
>
> 9. Mr Gates, why all that brain wash? You can fool some enterprise
> programmers but not the rest of us who used to hand-optimise our code,
> just to gain speed.
>
>
>
> Finally, a single word question to all those bright scientists who work
> for MS, Why ?
>
>
>
> Please don't try to change my opinion, you cannot. By the way I'm not one
> of those stupid guys who use to call Microsoft as M$. Me and all my
> colleagues use Microsoft development tools since 1982 and we all know what
> exactly are JIT, VM and native compiler.
>
>
>
> I really like .NET/WinFX as a library and C# as a modern language, but I
> feel sick with all that waste of processing power and lack of performance.
>
>
>
> Regards
>
> Ted Nicols
>
>


.

Relevant Pages

  • RE: Is that a joke ?
    ... > native code. ... It probably looks fast to Java or VB developers but what ... > about real time applications? ... > programmers but not the rest of us who used to hand-optimise our code, ...
    (microsoft.public.dotnet.general)
  • Re: Section 3.3.1
    ... Whether developers are willing to commit to ... writing serious applications for a platform is determined by how many ... apps for it? ...
    (comp.sys.mac.advocacy)
  • Re: Any .Net controls youd recommend?
    ... Microsoft is planning on doing). ... work arounds for God-only-knows how many other developers. ... distributed apps and save downloading the whole 25MB mess at once for those ... The majority of VB programmers were not ...
    (microsoft.public.dotnet.general)
  • Re: Success of VB
    ... programmers than C# programmers in absolute figurs. ... applications simply need to work in order to get some data processed. ... They just do not have as strict requirements as developers of, ... horrible C# code because they try to apply low-level tricks they were able ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Microsoft Losing Interest in C#?
    ... >> science to write functional applications. ... programmers than COBOL, C++, and Java programmers combined. ... after the waves of developers learning Java ...
    (microsoft.public.dotnet.languages.csharp)