Java's new AOT cache feature is in a rough state
Summary
Java's AOT cache aims to speed startup by training and reusing a cached state, but the feature is fragile in practice. The article highlights CPU feature mismatches causing crashes, fragile class linking, confusing logs, and limited documentation, comparing AOT caching with GraalVM Native Image. It argues that AOT caching is complex to use reliably in production and notes timelines around JEPs and future changes.