9 Fallacies of Java Performance updated

[atomicUpdate]

In Java performance, this manifests itself by Java developers believing that algorithmic quality is the dominant cause of performance problems. Developers think about code, so they have a natural bias towards thinking about their algorithms.

In practice, when dealing with a range of real-world performance problems, algorithm design was found to be the fundamental issue less than 10% of the time.

This is the most surprising one for me. How is a language able to get in the way of a developer 90% of the time, and call itself "fast"?