AdmiralCrunch wrote:
MyFutureSelfnMe wrote:
IMO Android is limited by heavy reliance on a language that uses a garbage collector (Java)
Dude,
NDK! I'm kicking some serious rear end on my Cortex A8.
Quote:
Yes, but I think that should be the *primary* way to develop Android apps.
1992 just called. It's was talking up 4GLs.
Seriously, there is
absolutely no way in H-E-double hockey sticks that any default programming language choice will ever go back to a 3GL.
<smarm>If we're at it, why not just go back to machine code? Think of the efficiency!</smarm>
How does the NDK help with the garbage collection cycle issue? How complex is the app you're developing? Have you noticed as I have that when working in a garbage collecting language you have to perform all kinds of ridiculous stunts throughout your code to avoid setting off the garbage collector, by keeping the objects created per frame down to just a few? Have you noticed that there are numerous standard library functions you can't even call during a frame because they might create an object? It's infinitely easier for me to work in C++ and control the deletion/scope of my objects. Not being able to create objects is diametrically opposed to OO philosophy!
Edit: DOH! You said NDK, not SDK. Sorry! At any rate, this issue totally discards Java as a language I can use to develop mobile apps, which is why I feel native code should be the default.