Isn't it really quite simple: Managed and non-managed languages make different fundamental trade-offs, opting for either performance or productivity when these are in tension.
Empirical evidence suggests t's easier to develop an Android application, but harder to make it feel fast. While it's harder to develop an iOS application, it's easier to make it feel fast. In other words, it's rare (if ever) you hear of an implementation of an app that feels snappier on Android than on iOS - even if iOS hardware is often inferior. /Casper On Saturday, April 14, 2012 10:13:53 PM UTC+2, phil swenson wrote: > > This guy claims: > > "Unfortunately, Java's designers didn't seem to value CPU time at all. > The language has a nasty reputation for sluggish interfaces, and its > execution speed drags well behind C++'s. Pointer aliasing or not we > are many generations of optimisers away from languages such as Java > overtaking C++ so if you need fast code C/C++ is the obvious choice." > > article here: > http://slidetocode.com/2012/04/14/objective-c/ > > discussion here: > http://news.ycombinator.com/item?id=3840861 > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/KFgl26W0VSAJ. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
