News for hackers. Stuff that matters.
Re:Android, evolvability and Comcast by awinter-py on Sunday April 23, 2017 @02:52PM (#14179720)
Then don't switch to JS, switch to C++ as the primary dev language. The performance-sensitive parts of the OS are already in C++ and the NDK exists, so this isn't that big a jump in terms of support from the android maintenance team.

C++ is not slower than java on constrained hardware, also is more respectful of memory. Is it harder to use? I don't think so but I may be in the minority here.

Re:Android, evolvability and Comcast by warcher on Sunday April 23, 2017 @03:31PM (#14179969)
C/Java interop is pretty painful still, and the tooling for native debugging in android studio is notoriously unreliable. (I hear it's better now, but I haven't had to get into those libs recently, so I can't say definitively. Last go round I had to roll Eclipse to debug ndk libs. Yeah. Eclipse.)
Re:Android, evolvability and Comcast by warcher on Sunday April 23, 2017 @03:40PM (#14180029)
I think this may have been intended as sarcasm, but yeah man. I do C development for my real high performance mobile development. Everybody does. If you saw an app and wondered "Oh wow, that was cool, how did they do that?!", more often than not, somebody wrote some nasty old C/++.