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

[Ron Pressler]

> On 5 Sep 2023, at 15:48, Peter Tribble <peter.tribble at gmail.com> wrote:
> 
> 
> That would be a pretty normal scenario.
> 
> A new version of the Java runtime could be pushed to a user by:
> 
> * The OS vendor, in a patch or update
> * If in an organization, by the organization's IT department
> * Ditto by an organization's security team 
> * Installation of a different application that updates Java as a side-effect

Sorry, I don’t understand. How *exactly* is your application launched so that it would use a different Java runtime when one was installed?

By the way, we also speculate about how different users do different things. When it comes to feedback it’s, therefore, best to limit things to what you yourself experience. One concrete example of something you experience is much more valuable to us than four examples of things you think others may experience.

> 
> And probably a number of others. The point is that virtually none of us live in a
> perfect idealized world; we generally have to work under the assumption that our
> code could be used in a variety of different environments, including different java
> versions, and that we have no control whatsoever.
> 

True, and that is why people wanted — and rightly so — to allow applications to better pick a Java runtime and control it. So we’ve worked for years on that and delivered a feature that allows any Java application to pick a runtime and configure it as it wishes (jlink). These days, if an application has difficulty choosing or configuring its runtime, it’s by choice. If lack of control over the runtime poses a problem for your application, why are you choosing not to control the runtime?

— Ron