This is my experience as well...
Posted Aug 24, 2011 9:00 UTC (Wed) by
khim (subscriber, #9252)
In reply to:
And THAT is the problem by alankila
Parent article:
HP dropping webOS devices
This sort of application should have its heap size tuned appropriately because too large heap will have lot of objects to collect when the cycle triggers, and this in turn can cause glitches, whereas a small heap will have frequent but fast enough collections.
Yeah. It works. But the main stated goal of the GC, it's raison d'ĂȘtre is the ability to forget about memory allocation. Remember: no memory leaks, no more confusion about ownership, etc? GC pseudoscience fails to deliver, sorry. Just like relational database theory fails to deliver. It does not mean both are useless - if your goal is "something working" they often are "good enough". But the problem with Java is the fact that GC is imposed. You can not avoid it because standard library requires it. So in the end you fight to the death with the one thing which should "free you" from some imaginary tyranny.
(
Log in to post comments)