Linked by Thom Holwerda on Mon 30th Apr 2012 19:17 UTC, submitted by bowkota
Permalink for comment 516704
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2007-07-27
Sure, if C++ is compiled into bytecode and run on adaptively JIT, then C++ can also achieve Java performance. Never mind.
My point is that Java can be fast, if you know how to do it. Have I proved my point? Java can be very fast, and rival C++. So, how is Java bad and slow? It is the fastest in the world.
I work in this business and NASDAQ is completely built in Java. LSE is built in C++. If you dont believe me, confirm this with guys that work at NASDAQ or LSE.
Also, these stock exchanges use commodity x86 servers. No special hardware, no risc cpus, no mainframes, or whatever. Just ordinary x86 servers. Typically with 32GB RAM and dual hexcore cpus, or so. Nothing special. Confirm this with guys working in the exchange business if you dont believe me.
Still my point is; if you know what you are doing, then Java can be fastest in the world, and Java exchanges rival or surpass C++ exchanges. So, Java is fast. But that requires knowledge. For instance, how do cope with the garbage collector in Java? I know how to do that.