Ask the Java Architect
summary
Covers concrete status and design choices: value types must support serialization and likely use constructor-based deserialization; records and switch expressions aim for JDK 14 (or 15) GA; text blocks preview returns to add escape/line-continuation fixes; Project Loom delivers virtual threads plus structured concurrency to make massive concurrency look like simple blocking code; Project Panama pushes a native memory API toward 14 with FFI and tooling to follow; GraalVM/native-image are options; checked exceptions stay.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:42serialization and value types in Project Valhalla
- 5:18Checked Exceptions
- 8:14Deprecation
- 9:27Thread API
- 11:01More deprecation
- 12:40Previewing
- 15:35Feedback
- 17:45Project Loom
- 21:37Reactive API
- 23:13Will Graul replace the standard JVM
- 25:52Data classes
- 27:01Switch expressions
- 27:35Type inference
- 28:47Unmodifiable collection initializers
- 30:42Extension methods
- 33:26Pipeline operator
- 35:45New reflection API
- 38:43Project Panama
- 41:01Vector API
- 42:36Module adoption
- 44:11Generics
- 46:36Modules
- 48:40Next big thing for Java
related talks
01h 11mModern Java: This is not your father's Java anymore
46mWhere is the Java language going?
50mJava Next - From Amber to Loom, from Panama to Valhalla
52mAsk the JDK Architects
01h 05mTo #Java 24 and Beyond
56mTo Java 22 and Beyond!
45mWhat's New in Java 21
45mJava Next - from Amber to Loom, from Panama to Valhalla