Linked by Thom Holwerda on Fri 3rd Feb 2012 23:43 UTC
Thread beginning with comment 505886
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2009-04-02
You know, it's funny... if somebody makes a comment about how many desktop Java apps run like ass, people are quick to blame programmers as well. Surely, it CAN'T be the languages that suck
No, it's the programmers. You can perform bad memory management in every programming language (including java).
Ex:
In C/C++ if you don't release memory, you'll get memory leaks
In Java or .NET: If you don't dispose objects the GC will not re-use their memory, and will keep requesting new memory blocks from the OS with every new().
Memory management is the responsability of the programmer, not the language (despite what some Java or .NET folks say).