Re:A Closer Look at Android RunTime (ART) in Android L
by mwcampbell on Friday July 04, 2014 @05:14PM
(#7990236)
I wonder if it would make sense to rewrite some native components of Android in Java now. Presumably, whole-program optimization means that the ART compiler is more effective if more of the code is in Java (or technically, Dex bytecode) rather than having opaque native parts with JNI overhead.
[ Parent
| on HN ]
Re:A Closer Look at Android RunTime (ART) in Android L
by DiabloD3 on Friday July 04, 2014 @09:44PM
(#7990777)
A lot of Android is written in Java already. What would be interesting, however, is Android transitioning to a message passing micro-kernel (instead of Linux) and writing as much as possible of the rest of the kernel in Java.
Re:A Closer Look at Android RunTime (ART) in Android L
by pjmlp on Saturday July 05, 2014 @12:16AM
(#7991008)
That is already the case. When you look at the NDK, you can only have access to game related API (audio, graphics and sensors) almost everything else involves JNI.
Re:A Closer Look at Android RunTime (ART) in Android L
by jordanthoms on Saturday July 05, 2014 @12:56AM
(#7991077)
Actually quite a bit of the view code is native still - start reading the source for View etc and you hit a level where it's mostly calls out to native libraries. e.g https://github.com/android/platform_frameworks_base/blob/mas...