> So your argument is that .NET doesn't perform as well as compiled code for > Win32?
In a nutshell. Reading http://msdn.microsoft.com/visualc/using/understanding/perf/default.aspx?pull=/ library/en-us/dndotnet/html/dotnetperftips.asp did not make the hype on JIT sound very compelling to me. Sounds awfully the issue of making DirectX perform - like tinkering with an engine through the exhaust pipe because the overhead on calls is so high. > What about the huge amount of research that quite clearly says that certain > kinds of optimizations done at runtime by smart engines allow p-code > applications in many ways to be _faster_ than their native code from the > start equivalents? Oh yes?. That would explain the performance of the java-only office suite? Now I am freely admitting to being very skeptical here but I am open to be convinced. A big shift in game development to .NET platform (clientside) I would find compelling - but instead I hear a lot of bitching. > What about the ability to distinguish between server side and client side > optimizations? Irrelevant on whole to most apps I would do. > The current win32 compiler market [for delphi at least] is a one size fits > all, .net clearly focuses on the ability to dramatically _improve_ > performance, not reduce it! > > Surely you don't believe what you just wrote? Perhaps needing a lot of convincing to believe the hype instead? I would have thought the .NET was pretty focused on, well, .net - performance and development speed for net applications maybe. (Aside from MS market issues anyway). A non-trivial openGL app running faster under .NET than under win32? ---------------------------------------------------------- Phil Scadden, Institute of Geological and Nuclear Sciences 764 Cumberland St, Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232 _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
