3 ms·
Native code runs on far more architectures than Dalvik, including (particularly) in the embedded world. And the NDK is a rather neat solution to the compilatio
by jnbiche 12y ago
Native code runs on far more architectures than Dalvik, including (particularly) in the embedded world.
And the NDK is a rather neat solution to the compilation issue. Once you've set up the toolchain properly, different architectures are simply not an issue. There's no architecture that Android runs on that doesn't accommodate native code.
After all, don't forget that under a rather thin layer of Java, the native code "cancer" is what is driving Android.
- kllrnohj 12y agoHogwash. If you are talking about SOURCE portability, Java runs in just as many places as C code, including in the embedded world. If you are talking about BINARY portability (which is what everyone was actually talking about), then native code isn't portable for shit, whereas Dalvik code happily runs on multiple flavors of ARM, MIPS, and x86 with official or partially-official support. Unless you are proposing that Android adopts a Goobuntu design of "compile everything from source", then the portability of native code source is utterly irrelevant. And if you are proposing that, you are hopelessly naive. Not to mention you must really, really hate having battery life if you want to spend over an hour compiling & installing, say, Firefox.
- deleted 12y ago[deleted]