How it felt like
summary
Java development narrows to three concrete pressures this year: security scanning of foundation AI models to verify provenance, custom JRE via jlink shipped in the JDK for minimal deployments, and tooling-driven collaboration to tame legacy “don’t touch” modules. The claim is that without upgrading tests and adopting platform features like GitHub Codespaces and Copilot (GPT‑4) teams cannot raise quality; examples stress team structure, concrete collaboration patterns, and using built-in packaging to reduce runtime surface.
AI-written summary · about
related talks
03h 35mJava ON 2024 Day 1
45mJava Innovations - from Developer-driven features to (...)
50mKeeping up with Java: Look at All These New Features!
55mRapid Java Innovation
54mJava Forever (Round Table).
43mHow to (Re)start Your Java Journey in 2026
27mNo QA: Modern Java: Change is the Only Constant
42mEnhancing Productivity and Insight: A Tour of JDK Tools Progress Beyond Java 17