"Unfortunately, Java's designers didn't seem to value CPU time at all. " Well, it's obvious that people think of (Apple) fanboism when they read such misinform

"Unfortunately, Java's designers didn't seem to value CPU time at all. " Well, it's obvious that people think of (Apple) fanboism when they read such misinformation; apart from the fact that there's no point in writing such statements without citing some numbers or real cases. I can tell you that I've written my last line of C++ exactly ten years ago. In these ten years I've designed and implemented a good deal of industrial software in different segments and never experienced performance problems. Already in 2004, which is ages ago, I designed and implemented a near real time system for distributing telemetry data in F1 racing - among others, Renault won two championships running that system. It was Java 1.4 and it worked pretty well. The specs were pretty demanding. I recall people wondering whether Java was up to the requisites (at the time it was a reasonable doubt, not today). I am just lucky as I can mention a publicly known project, but there are tons of people around who daily experience excellent performance with Java and don't feel any desire to go back to C/C++. You'd just attend a couple of Java conferences (or at least read the slides) before publishing uninformed statements.