JNI will probably never truly die, but it's reasonable to assume that it will eventually become restricted in similar ways. The motivation is simple: applicati

JNI will probably never truly die, but it's reasonable to assume that it will eventually become restricted in similar ways. The motivation is simple: applications should become the arbiters that decide which modules get to invoke native code. Libraries don't get to nilly-willy call non-Java code anymore. If, say, a dependency upgrade introduces changes that involve a new native call, it will be very noticeable.