News for hackers. Stuff that matters.
Re:Why Startups Could Use .NET, But Don’t by MichaelGG on Tuesday May 17, 2011 @04:45PM (#2557838)
Here's a few things:

1. JVM cannot do unsafe code. In the CLR, you can create unverifiable IL and do pointer manipulation, etc. Raw memory can be free accessed however you like. That's a handy interop and performance feature.

2. JVM doesn't support structs. Again, performance difference. (Although, sometimes the CLR's JIT hasn't emitted the best code for structs.)

3. The CLR has generics. In Java, generics are implemented via erasure. This has an impact on performance and reflection.

Re:Why Startups Could Use .NET, But Don’t by agazso on Tuesday May 17, 2011 @05:23PM (#2557974)
You can use JNI from Java if you need performance. It is the "unsafe but fast" option.
Re:Why Startups Could Use .NET, But Don’t by electrum on Tuesday May 17, 2011 @06:50PM (#2558284)
Re:Why Startups Could Use .NET, But Don’t by Todd on Tuesday May 17, 2011 @05:23PM (#2557976)
In addition, the JVM is just that--a VM. The platforms that run .NET with a JIT compile the IL down to optimized native code. This is similary to the way many Lisps work. Although the JVM is highly optimized and runs faster than Mono in many tests, it will always have an inherent performance disadvantage.
Re:Why Startups Could Use .NET, But Don’t by zmmmmm on Tuesday May 17, 2011 @06:19PM (#2558181)
Surely you can't be unaware that the JVM has a JIT?
Re:Why Startups Could Use .NET, But Don’t by Todd on Friday May 20, 2011 @02:23AM (#2566647)
Ah, things have obviously moved on since I left the Java world years ago. In any event, the VM is still specified at the bytecode level. The JITs are optimizations that are outside of the standard. The .NET ECMA standard specifies an IL that is designed to be JITed to native code.

To the parent question, the performance is very close on the two platforms. The point I was trying to make is that the .NET platform does have some things in it's favor at the IL/VM level.