I didn't view the video, but it sounds like he was on target. "Modern programming techniques" is often a euphemism for "sloppy programming techniques", and one sloppy technique is not adjusting your style to the environment and environmental limitations. In this case, on a slow box with a clunky GC implementation, great effort needs to be put into minimizing the rate of heap consumption if one wishes to avoid GC "pauses".
The guy may have been extreme in his suggestions, but the general direction would be correct. On Oct 20, 1:43 am, Peter Webb <[email protected]> wrote: > > The first thing I recommend watching is this google > > presentation:http://www.google.com/events/io/2009/sessions/WritingRealTimeGamesAnd... > > I think the advice given in this video is basically wrong. > > It is a presentation done by a C++ programmer who has just written his > first Java program. His idea of managing GC lag is to not instantiate > any classes at all in real-time sections of the code. He spends a > great deal of time explaining how difficult that is. > > This flies in the face of modern software design, which says build it > right then build it fast. He basically says throw away most of the > benefits of using auto-GC languages such as Java by writing your code > in a very artifical way which avoids allocating memory. > > It is a pity because he could have told us some things we (or at least > I) don't know, such as how the GC is triggered, whether it is device > dependent, whather there are calls to suspend repacking the heap, > practical stuff about how to best use a GC language for real-time > apps. Trying to avoid anything at all which might cause GC to happen > is throwing the baby out with the bathwater. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
