The future is native
summary
Packed objects prototype shows a concrete encoding: objects become (target+offset) headers so Java can map on‑heap or native structs, with examples of hash tables, nested points, and a layoutFactory that maps addresses to accessors. The talk describes tooling gaps (no stable LDL parser yet), memory model decisions (containers, atomicity, endianness, alignment), JNI/Unsafe tradeoffs, DDR use, lifetime and security risks, and open API experiments toward project Panama and layout descriptor language—practical design experience, not just theory.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:59What am I talking about
- 3:12Hash table example
- 5:38Packed objects
- 10:05Java
- 13:21Packed
- 19:15Volatility
- 21:46Layouts
- 26:42Layout Factory
- 28:24Memory Locations
- 29:48Containers
- 35:10Effective addresses
- 36:40Stackmap tables
- 38:04Memory lifetime
- 39:44existential questions
- 40:08experience
- 40:42get involved
- 41:48legal notice
related talks
01h 01mNative Code, Off-Heap Data and Java
51mNative Interoperability with JDK 25 and the FFM API
36mA Promising Future for using Native Libraries in the Java World
55mBare metal Java
01h 01mJava Enable Preview: Foreign Function and Memory Interface
39mMost impacting features of newest JDKs
46mBare Metal Java
01h 04mProject Panama Unleashing Native Libraries