2 ms·
Maybe I am too, but that phrase just bugged me. Surely there are other reasons to use these tools than just "explicit memory management?" I suppose I could sa
by sramsay 13y ago
Maybe I am too, but that phrase just bugged me. Surely there are other reasons to use these tools than just "explicit memory management?"
I suppose I could say, "I haven't used any JVM languages, because I haven't felt the need to gouge my eyes out over memory errors I can't control."
- jtheory 13y ago> Surely there are other reasons to use these tools than just "explicit memory management?" Sure, though he does mention he's biased by the projects he works on (generally web apps/services -- not device drivers, image processing, realtime anything, etc.). > I suppose I could say, "I haven't used any JVM languages, because I haven't felt the need to gouge my eyes out over memory errors I can't control." The phrase that bugged you wasn't cast as an insult, though, and yours is... mysterious; Java's GC is quite stable, so any memory-related errors are under the coder's control. "Memory errors" being basically just "using too much memory", as I've never seen any other type of memory error in Java. Maybe you could say "I haven't used any JVM languages, because I've never felt the need for automated memory management"? That assumes Java has nothing else to offer.