Linked by Thom Holwerda on Sat 27th Apr 2013 15:47 UTC
Google "As everyone is trying to guess whether the next big Android update is going to be Key Lime Pie or not, and whether the release will be Android 5.X or 4.X, we have yet to hear anything concrete. After getting a tip from an eagle-eyed reader (thanks, deepayan!) and digging deeper, I can definitively tell you that Google is currently working on Android 4.3, and it is still Jelly Bean." Great detective work by Artem Russakovskii.
Thread beginning with comment 559925
To read all comments associated with this story, please click here.
Makes sense
by reduz on Sat 27th Apr 2013 18:18 UTC
Member since:

why change something that works so well?

Reply Score: 0

RE: Makes sense
by jayrulez on Sat 27th Apr 2013 19:19 in reply to "Makes sense"
jayrulez Member since:

To make it work even better.

Reply Parent Score: 3

RE: Makes sense
by moondevil on Sat 27th Apr 2013 19:54 in reply to "Makes sense"
moondevil Member since:

Let me see:

- Support Java 7 language constructs (most likely not going to happen with the Oracle suit going on)

- Compile Java to native code or improve the JIT

- Allow the full use of native applications, instead of shared objects loaded into Dalvik with wrappers around JNI calls

- With clang as part of the NDK, start supporting Objective-C instead of disabling it

- Even without generics (my pet peeve), allow for Go usage in the NDK via gccgo

I think I can remember of a few more issues from the developer point of view.

Reply Parent Score: 4

RE[2]: Makes sense
by JAlexoid on Sun 28th Apr 2013 00:09 in reply to "RE: Makes sense"
JAlexoid Member since:

1. There will be no upgrade to Java7 or even Java6, because Java6 changed the code license to prohibit exactly what Google are doing.
2. It's already mostly compiled
3. Full native applications have been available since 2.3
4. There will be no Obj-C, because the UI library(Skia et al) does not work with Obj-C. Enabling Obj-C is rather useless, since most iOS game devs are already on C++. And Obj-C UI code will definitely not be even close to compatible
5. Go would be nice

Reply Parent Score: 3

RE[2]: Makes sense
by reduz on Sun 28th Apr 2013 02:44 in reply to "RE: Makes sense"
reduz Member since:

Having to interface with Java from C++ is a royal pain in the ass. JNI sucks.
Nothing would make me happier if Android API moved to C++ (or at least the full API was exported to NativeActivity)

But it's still pointless because clients want integration with APIs such as facebook, gree, tabjoy, adwhirl, etc. and all those are java-only.

Reply Parent Score: 4

RE: Makes sense
by vivainio on Sat 27th Apr 2013 21:25 in reply to "Makes sense"
vivainio Member since:

Android is far from perfect yet. Multitasking is out of hand a lot of the time, and performance overall is not as stable as it should be.

It's not far away though.

Reply Parent Score: 4

RE[2]: Makes sense
by Kochise on Sun 28th Apr 2013 07:09 in reply to "RE: Makes sense"
Kochise Member since:

From a former Symbianer, I could tell it's not all that bad...


Reply Parent Score: 1