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.
Permalink for comment 560023
To read all comments associated with this story, please click here.
RE[5]: Makes sense
by moondevil on Mon 29th Apr 2013 07:59 UTC in reply to "RE[4]: Makes sense"
moondevil
Member since:
2005-07-08

2. Hot code = most used = mostly compiled.


That is not the same as you don't have to endure a JIT overhead. That is the reason .NET is compiled to native code in Windows Phone 8.

3. Considering why NativeActivities were created and the main language of Android you will not get rid of that. Same issue as with calling Objective-C from C++, there will have to be a converting step somewhere.


There is no conversion going on with Objective-C vs C++.

Both languages have native compilers available, and you can even make use of the Objective-C++ compiler mode.

There is no interop performance penalty between language implementations.

4. And what would be the point of porting application code that is highly dependent on iOS frameworks?


I don't know, code reuse? GNUStep also offers quite a lot of similar APIs.

Additionally it is always a matter of how much care is taken writing portable code.

Games for example have their own UIs built with OpenGL.

Reply Parent Score: 3