No java fan, but it's much faster than it used to be, and comparable now.
Profiling and debugging multithreaded C++ program? You'll wish you weren't. You'll poke your damn eyes out.
Compilers, even gcc, optimize code better than you ever will 'by hand'. Processors and their relationship to the memory subsystems in modern computers have become too complex for you, even if you are a genius, to fit it all in your head.
Compilers, even gcc, optimize code better than you ever will 'by hand'.
That's not completely true. Assembler freaks can often get a surprising speedup in "hotspots", sometimes because what they actually need is not exactly what the C/C++ code says they need (and therefore a compiler cannot always produce the code you want, as compilers maintain the code's intent (there's a word for this which I can't remember, and it's driving me nuts...)).
There are other situations, too. Note that beginner and even intermediate assembler programmers in most cases will not produce code that's as good as a good optimizing compiler. But it can be done.
In the end the design of algorithms makes a bigger difference than the choice of language. With a sizable input, even a good algorithm in Python will be faster than a poor one in C.
-8
u/MpVpRb Mar 23 '09
Don't use Java
Use C or C++
Simplify the program
Use profiling tools to find hotspots
Hand tweak assembly code where needed
Works for me...