djinni and D

[Paulo Pinto via Digitalmars-d]

On Monday, 13 April 2015 at 13:56:14 UTC, Ola Fosheim Grøstad 
wrote:
> On Sunday, 12 April 2015 at 19:37:43 UTC, w0rp wrote:
>> It uses Objective-C++ to connect to iOS with Objective-C, and 
>> JNI to connect to Android with Java.
>
> How fast is JNI now? I believe the now defunct Mosync framework 
> compiles C++ to a VM emulated on JVM...

Depends on which JVM you are speaking about.

As for the official Java JVMs (not Android), Mark Reinhold 
acknowledged that JNI was made hard on purpose to force 
developers to try to avoid writing platform specific code.

Now that Oracle is trying to get the last mile in terms of 
performance given the increase of Java usage in the data centers, 
the JNI will get replaced as part of the Project Panama, 
currently targeted for Java 10.

The bindings are based on the experience with Java Native Runtime 
and his being driven by Charles Nutter, one of the JRuby 
developers.

http://openjdk.java.net/projects/panama/

In any case I doubt the Android team will do anything about it, 
looking forward to Google IO 2015, to see if there will be any 
announcement regarding either the dropped NDK support (not 
available in AS) or if Java 8 will ever be supported.

Given the GCJ zombie code in the GCC, they could have brought the 
CNI back to life with ART, but not even that.

https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcj/About-CNI.html