On Feb 3, 12:50 pm, Casper Bang <[email protected]> wrote: > > Apple places a > > good user experience ahead of developer needs. And users want good > > battery life which conflicts with "free-range multi-tasking". > > Yeah but I just have to wonder whether at some point, "free-range > multi-tasking" won't be needed at the programming language level just > as is the case on desktops. Mobile CPU's won't scale much higher than > the current 1GHz and multi-core designs are here to stay. Due to power > leakage, a rule of thumb states that a doubling in frequency, > quadruples the power consumption. This means that you can cut power > consumption in half by adding another core and run these at half > speed.
Agreed - iOS devices will go dual core this year and maybe quad core next. > At some point (4 cores?) it becomes fairly important that work can be > split up and less important what a background service might be doing. > It occurs to me that the homogeneous Android stack will scale easier > in this future scenario. I've heard Android being called many things, but "homogenous" wasn't among them, yet. :-) As mentioned before, iOS has strong multi-threading, so I'm not sure why Android has an advantage there. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
