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 560040
To read all comments associated with this story, please click here.
RE[6]: Makes sense
by JAlexoid on Mon 29th Apr 2013 12:14 UTC in reply to "RE[5]: Makes sense"
JAlexoid
Member since:
2009-05-19

That is not the same as you don't have to endure a JIT overhead.

And unlike traditional JVMs, the compiled code is preserved between VM shutdowns. There is a lot more GC overhead, than there is JIT and interpreted code overhead.

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

Objects are not the same. Method calls are not the same.

I don't know, code reuse?

Which is not an issue of any sizeable amount.

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

And Objective-C is objectively barely portable. C/C++ on the other hand...

Games for example have their own UIs built with OpenGL.

And are mostly written in C++ for simplicity.

Reply Parent Score: 3