I started coding on a 1Kb ZX-81 (http://en.wikipedia.org/wiki/Sinclair_ZX81), but that doesn't mean I'd expect to see the same problems and limitations on "modern" hardware, and I do see the stack depth limitations as tweaky.
Dianne has already pointed out that even the guys at Google consider it a less than optimal, lets hope a 1.6 or whatever brings some improvements. Al. P.S. If 16Kb RAM makes you a greybeard I'd better start getting ready to draw my pension :). --- * Written an Android App? - List it at http://andappstore.com/ * ====== Funky Android Limited is registered in England & Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Murphy Sent: 25 April 2009 14:05 To: [email protected] Subject: [android-developers] Re: Layout bugs jarkman wrote: > Mark - I've spent a lot of time developing for a lot of mobile > platforms. It's true that they all have their quirks, and they all > need a bit of tweakiness, but this stack business seems to me to be > more than ordinarily tweaky. *shrugs* It all depends on what you're used to. I'm a graybeard. I had been programming various machines and languages for a decade-plus before I got my hands on anything with the G1's specs. When you cut your teeth on developing in 16KB of RAM total, dealing with the Android stack depth issue isn't terribly "tweaky". <insert obligatory get-off-my-lawn rant here> > Now it's more awkward. Reworking existing layouts, using more > laborious techniques when making new ones, building a UI to economise > on views instead of to serve the user, having to measure the deepest > possible nesting in an environment where views can be built at runtime > - none of this is helpful. > > I expect we are stuck with the teeny stack for 1.5. I'm sure the > Android engineers haven't gone this way for trivial reasons, and I'm > sure they won't change it just because I have a moan about it. But, > I'd like to be clear that this is not just an 'excuse for a bit of > optimisation' - it's a real (even if unavoidable) step backwards. Don't get me wrong -- I'm just trying to help explain and assist with an unpleasant situation. In an ideal world, view depth would not be an issue, because Android would either use less stack per view layer or would have, say, double the stack space. Of course, in an ideal world, my G1 would have as much horsepower as my quad-core desktop, battery life longer than my Prius, and would have Natalie Portman in my speed-dial. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
