What are we going to do about mobile?

[rikki cattermole via Digitalmars-d]

On 12/04/2017 10:54 AM, Russel Winder via Digitalmars-d wrote:
> On Wed, 2017-04-12 at 10:43 +0100, rikki cattermole via Digitalmars-d
> wrote:
>> […]
>>
>> JNI itself isn't hard to work with, its mapping classes for D easily
>> to
>> it which is hard. Especially when inheritance comes into play.
>
> JNI is on notice for being retired, but clearly this is Java so
> sometime next century. The replacement won't be here for a while, but
> it will be here.
>
> http://openjdk.java.net/jeps/191

Considering it was created in 2014, I think we're safe implementing 
extern(JNI) support either which ways.

Although a little strange since nobody has completed a full JNI 
implementation yet!