4 ms·
And after all those years, you should kinda understand that this is not going to change. JNI is how Java communicates with native code and neither Oracle or Goo
by izacus 8y ago
And after all those years, you should kinda understand that this is not going to change. JNI is how Java communicates with native code and neither Oracle or Google are going to change that. What's the point of complaining for YEARS about this? Why are you losing energy over that, it makes no sense?
- Cyph0n 8y agoComplaining is a good way to get companies to improve things. You may think that it's a lost cause, but others have the freedom to think otherwise.
- pjmlp 8y agoAgain, improve your reading skills. Android J++ as Java fork could pretty much use something else other than JNI, after all they are using another VM to start with. Second, even with JNI, there is a big difference between forcing millions of developers to write boilerplate by hand, and offering an Android Studio based tool that would automate the grunt part of the work. Finally, update yourself with the Java world, Oracle is indeed bringing forward a JNI replacement. http://openjdk.java.net/projects/panama/ http://openjdk.java.net/projects/panama/ Which, naturally will never arrive to Android J++, but that is a discussion for another day.