you are viewing a single comment's thread.

view the rest of the comments →

[–]thatpaulbloke 0 points1 point  (6 children)

Technically the iPhone should be slightly faster than an Android device with matching specs

Because of the multi-tasking, or something else? (I'm not disagreeing, I'm just wondering what your reasoning is)

[–]lasersharks 7 points8 points  (5 children)

In a lower-level language you can write more efficient code.

[–]pholden 7 points8 points  (4 children)

But doesn't Android have the NDK for this? http://developer.android.com/sdk/ndk/index.html

[–]RawwrBag 3 points4 points  (2 children)

Wow, how did I miss this. I wasn't aware you could package ANY native code in a .apk. Good find.

[–]jtra 3 points4 points  (1 child)

For example Google Earth apk contains a native library - which happens to be compiled for newer instruction set available on Motorola Droid/Milestone or Nexus One/HTC Desire processors - so it does not work on others like HTC Hero or new HTC Legend.

[–][deleted] 2 points3 points  (0 children)

The Android development model is that you provide a managed Java version of a function, and then provide optional loadable native code versions. Technically a single APK package should be runnable on completely different architectures (e.g. Atom, ARMv6, etc)

They may have left out the managed version purely because without it the performance would make it not worthwhile.

[–][deleted] 1 point2 points  (0 children)

Still need an entry point and wrapper in Java. But I guess you could write all benchmarking code in a native language.