What a weird, unhinged take. Android is mostly written in C, Android apps are AOT/JIT compiled when written in Java, and the NDK lets you write/port from whatever native you have, which is how you get Chrome to run on it to begin with.
replyThere's no JVM in Android. Never has been.
replyWhat's the point of the complaint? Is there anything better that is commercially viable?
replyYour Linux based dream phone is not going to sell more than 10 units.
I think they might be saying that there's still no supported way to build a native-code app on the Android OS. It could be construed as a plea to make that happen in order to unlock greater performance, not necessarily a desire to have a DIY Linux-based OS option.
replyThere's NDK which seems supported. It's been some years since I messed with mobile stuff but https://developer.android.com/ndk
replyIgnoring the native vs java runtime interface application difference between Android and iOS, which the top poster was was referencing.
replyYour Linux phone statement is a fallacy.
Ask FuriLabs how many of their phones they have sold.[0] High confident it is more than 10.
FuriLabs moved their batman, battery monitoring application, from Python to C and it really improved performance. Native applications really do keep resource usage low and is beneficial.
They don't publish sales numbers, but I've never seen one. So probably somewhere between 10 units and significant market share.
replyI believe the comparison is with iOS not Linux. Android is Linux after all. It’s just that most programs don’t get to run a that level of abstraction, and instead run on top of a jvm. At least in iOS the code does seem to be able to be more efficient due to to higher usage of natively compiled code, which is what I think the op was complaining about.
replyThere's no JVM in Android. Most important parts of an Android app are compiled ahead of time into CPU machine code, rarely used parts are compiled into machine code in runtime using JIT.
replydeleted
reply