About this episode
The Java runtime offers a host of guarantees like memory safety, type safety, encapsulation, and many more. What makes these aspirations actual guarantees is a property called "integrity". But there are a few mechanisms in Java that allow undermining integrity - some for good, some for less good reasons. Integrity by default states that all such operations need to be disabled by default. Today we discuss why that is so important, what the progress toward this goal has been, and what Java developers need to know to keep their applications going.
Nicolai Parlog talks to Ron Pressler, who is Java Architect at Oracle and, among other things, lead of Project Loom.
Get every episode summarized
Each time Inside Java publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Inside Java
"Make Java Safer with Flexible Constructor Bodies" [IJN]
Inside Java
"Ask the Architects at JavaOne'26" [AtA]
Inside Java
"You Must Avoid Final Field Mutation" [IJN]
Inside Java
"How JDK 26 Improves G1's Throughput" [AtA]
Inside Java