On Sun, Apr 12, 2009 at 6:07 PM, JP <[email protected]> wrote: > On Apr 12, 4:49 am, Mariano Kamp <[email protected]> wrote: > Devels have got to understand how the underpinnings work and how to > create efficient apps that use the thread model proper, set timeouts > etc. etc. That object instantiation and garbage collection are so darn > expensive operations adds considerably to the challenge. >
True, programming for mobile devices is quite different than programming for PCs, and devs should do their best to code appropriately, *but* Google needs to do better as well: 1. There *has* to be some kind of JIT, and IMO the the easiest way to do it is for apps to get JITted on installation, somewhat similar to what Microsoft's ngen tool can do to managed/.NET apps. I realize this would double the space needed for the app's code, but no user would complain if apps start running noticeably faster automagically. If writing a JITter for every CPU is unacceptable, then at least do the best at compile time, inlining obvious getters and setters, replacing member variable access with locals in loops, detect common loops over standard collection classes and cache .size(), etc., etc. 2. The GC needs improvement - the current GC is *very* slow 3. If Google can't fix 2) they need to provide developers with some sort of standard API for creating and maintaining object pools, and educate devs (especially game devs) how to use it because right now everyone reinvents the wheel. Cheers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
