Comment Re:Java too complex (Score 1) 558
This is strange. I recall reading a lengthy article about how Java got list sorting to use roughly the same number of cycles as C. My guess is either you used the wrong algorithm, used a poorly optimized JVM, or had some other setting set wrong. If Java was consuming more memory, you could be losing all your performance to garbage collection. But my experience with Java, sorting lists several hundred thousand items long, was that it worked perfectly fine and was very quick.
Or he sorted a user defined type, which has to be a class in Java. In C#, it can be a struct. Java benchmarks often use sorts on primitive types, but real-world apps often have to operate on user-defined ones.