[External] : Re: JEP draft: Prepare to Restrict The Use of JNI

[Peter Tribble]

On Tue, Aug 29, 2023 at 5:25 PM Alex Buckley <alex.buckley at oracle.com>
wrote:

> On 8/29/2023 8:35 AM, Attila Kelemen wrote:
> > That is a completely invalid argument. I wrote "many people proposed
> > basically the same thing", and then you try to refute it by stating that
> > there was one guy who didn't. This is a non-sequitur. Secondly, your
> > claim is not even true, because Glavo wanted to set a flag in the main
> > module. That is not zero flag no matter how I count it.
>
> The whole point of this JEP is to give the choice of enabling JNI to the
> user. If a library developer can enable JNI by saying `requires native;`
> in a module, then the choice isn't given to the user.
>

However, it's not really a choice. The only alternative for the user is to
not
use the application *at all*.

And that's what I see as the problem here. There are no possible actions
that will improve the ecosystem or the software. There is no better path
that developers/users get guided towards. The only possible course of
action is to --enable-native-access and carry on.

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20230829/25fb2d83/attachment.htm>