Linked by Thom Holwerda on Sat 8th Oct 2005 18:40 UTC, submitted by anonymous
Java Programmers agonize over whether to allocate on the stack or on the heap. Some people think garbage collection will never be as efficient as direct memory management, and others feel it is easier to clean up a mess in one big batch than to pick up individual pieces of dust throughout the day. This article pokes some holes in the oft-repeated performance myth of slow allocation in JVMs.
Permalink for comment 42356
To read all comments associated with this story, please click here.
Member since:

"As for the runtime performance you claim there is no difference between C++ and Java when all evidence shows the opposite."

Where is this evidence? So far the only evidence you have provided is a benchmark that everyone except you agrees is hopelessly flawed.

"Benchmarks end public perception conclude that Java is slow -- end of story."

I've quoted scientific studies that say it is not. What have you quoted? A benchmark that everyone agrees is hopelessly flawed.

Reply Parent Score: 1