But doesn't that map to Java's ExecutorService and Future etc? I think there's some stuff needed further down as well, Dalvik is after all not the JVM... thankfully.
On Feb 3, 6:39 pm, Kevin Wright <[email protected]> wrote: > On 3 Feb 2011 17:32, "Casper Bang" <[email protected]> wrote: > > > > > > > > > > > > > > I think the iOS programming model is simpler than the Android one > > > (e.g., no concept of activities). > > > That's my favorite, very decoupled and each to hook together in a > > modular way. > > > > 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. > > > But isn't GCD just a scheduler optimized for task parallelization? The > > one advantage I *do* see that iOS has, is support for closures... but > > hopefully Java... ahrm... Android will also get this sometime before > > we retire. :) > > Alternatively, just use scala, clojure, jaskell, jython, jruby or fj... No > need to wait, and they all offer garbage collection :) > > > -- > > 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]<javaposse%2Bunsubscribe@googlegroups > .com> > .> For more options, visit this group at > > http://groups.google.com/group/javaposse?hl=en. > > > > > > > > -- 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.
