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 42093
To read all comments associated with this story, please click here.
I agree...
by suryad on Sun 9th Oct 2005 04:15 UTC
suryad
Member since:
2005-07-09

...with the poster who said Java is all about ease of programming. Sure it is not perfect but then again neither is every other programming language out there. Java should be used with discretion...it is great in certain situations but not in all. Java is not about how fast the program starts up but rather how fast the program runs once the program has booted up.

There is no denying that Java is a great technology so for those naysayers...shut up. But there is no denying that there are loads of languages that are great for writing apps which we are used to using as an end user like chat clients, word processing suites, etc etc that run really really fast when compared to their written-in-Java counterparts.

All I am trying to say is Java is not perfect. They are trying and the technologies it has brought about are quite interesting to say the least.

Reply Score: 1