Inside Java Newscast #73 // nipafx

Java has been working toward 'integrity by default' for over a decade, aiming to ensure that operations which undermine platform integrity — such as deep reflection via setAccessible, sun.misc.Unsafe, JNI native code, and dynamic agents — are disabled by default and require explicit command-line opt-in. A draft JEP now ties these efforts together. Key milestones include strong encapsulation becoming default in JDK 16, JEP 471 deprecating Unsafe memory-access methods in JDK 23, JEP 472 proposing JNI warnings in JDK 24, and JEP 451 warning on dynamic agent loading in JDK 21. The goal is that without specific command-line flags, a Java program's integrity — covering maintainability, security, and performance — is fully guaranteed.