The author makes several claims, of which unfortunately, I could only agree with the final one. Claims: 1. Projects that shouldn't be written in a scripting l

The author makes several claims, of which unfortunately, I could only agree with the final one. Claims: 1. Projects that shouldn't be written in a scripting language should be written in C++, not Java because it is more efficient. [Author probably hasn't spent enough time debugging other people's C++ which blew up or leaked memory on customers sites] 2. C++ is a better long-term choice (for people who don't poke themselves in the eye with sharp objects) [Precisely. Just like seat belts are only useful for people who have an occassional accident] 3. C++ gc library is as good as Java's GC. [No, listen to Cliff Click's talk. A VM defines boundaries between what is a programmers task, a language's task and a runtime's task.] 4. Java consumes more memory than C++ for equivalent tasks. [The standard class library can be big. Including iostreams in gcc results in 1Mb executable.] 5. Java runs slower [The purpose of programming is to get to the solution to a problem the fastes - Guy Steele. Java has enough safety features.] 6. If you know C++ you know Java (because C++ is bigger) [precisely.] 7. Java is an evolutionary dead-end in language design. [that is only because Java doesn't have Anders Hejlsberg.]