On Feb 3, 4:06 pm, Casper Bang <[email protected]> wrote: > > I've heard Android being called many things, but "homogenous" wasn't > > among them, yet. :-) > > A reference to the fact that the programming model on Android does not > concern itself with the type of background task (like most computing), > it's more general purpose whereas the iOS model seems very task > specific.
I think the iOS programming model is simpler than the Android one (e.g., no concept of activities). > > As mentioned before, iOS has strong multi-threading, so I'm not sure > > why Android has an advantage there. > > It doesn't directly, but you have more options, say i.e. you wish to > make use of Scala to press as much performance out of the cores as > possible. This remains hypothetical, Dalvik is probably not yet geared > for this in the same way as the JVM is. I think that on iOS, the CPU can multi-thread more efficiently (Grand Central Dispatch), but you only have the three ways of threading that Apple gives you. On Android, thread switching is probably not as efficient (JVM on top of Linux), but developers will probably have more options for implementing multi-threading in the future. -- 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.
