Java Urban Performance Legends
An anonymous reader writes "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."
Here or use the Firefox extension.
So what you're saying is that KTorrent is just Azureus recoded in C++? If so, your argument is rock solid. Otherwise, you really are comparing apples and oranges.
I can come up with two implementations of a non-trivial task that "do the same thing" where one is orders of magnitude faster than the other, regardless of the language it is coded in.
Unless you are comparing essentially the same implementation, the comparison is meaningless.
all the energy released by a an article that is conceptually flawed... it is supposed to be an engineering discipline. engineering disciplines are about using the mathematical models to make appropriate decisions trading off different abilities to get the best "fit" for the desired result. verticle and horizontal understanding of technologies, their uses, strengths, weaknesses, & costs can be a complicated. as shown by the replys to this article. too bad such energy isn't funnelled into create better usable models about how to make technology choices for the job at hand...
Let's see an OS written in java, then.