"Daniel James"  wrote

| It's really hard to concoct a fair test. JIT-compiled code will always
| suffer a small speed penalty for the time it takes to do the JIT
| compilation, but may be faster than compiled C code thereafter because
| the JIT compiler is able to make some whole-program optimizations and
| is able to target the actual processor in use rather than generating
| generic x86 or AMD64 (or whatever) code.
|

  That's optimistic. But it still doesn't account for the
fact that in most scenarios it's also hobbled by wrappers.
If you want the convenience, RAD, and safety of .Net
then you're not using direct system calls. Every object
reference is going to cost you. You're calling to the
framework, which then has to call the system file. .Net
is not Win32 API. It's an additional layer in most cases.

--- SoupGate-Win32 v1.05