>>9 Manual memory management is an essential part of programming.
Any proof? I don't think so. Manual memory management is useful in certain types of applications but it hardly is essential.
Name:
Anonymous2011-10-02 15:53
People who are against GC have never programmed anything but small, linearly structured script-like programs. If you're running a single thread, you can go ahead and allocate something, send it off to perform a task, and then wait for it to come back and kill it, since you can only do one thing at a time anyway. But when you're dealing with threads and concurrency and workers and asynchronous callbacks, it's not that simple. Either you must write your own not-as-good-as-language-x's garbage collector specifically for the program, or just end up shipping another hideously memory inefficient Windows application.
So keep on talking trash about CG while you hack away at your 200-LOC ``hello world'' app from 1982. Since you'll probably end up being a janitor it's good that you're learning to collect garbage.
They weren't called apps in 1982. How I wish I could go back to that time.
Name:
John Carmack2011-10-02 18:08
The biggest problem is that Java is really slow. On a pure cpu / memory / display / communications level, most modern cell phones should be considerably better gaming platforms than a Game Boy Advanced. With Java, on most phones you are left with about the CPU power of an original 4.77 mhz IBM PC, and lousy control over everything. [...snip...] Write-once-run-anywhere. Ha. Hahahahaha. We are only testing on four platforms right now, and not a single pair has the exact same quirks. All the commercial games are tweaked and compiled individually for each (often 100+) platform. Portability is not a justification for the awful performance.