So you're now weighing the increased container pull time (due to size) vs the class load time you're saving through the cache.

It's nice to at least have the option of making that tradeoff

(And I suspect for plenty of applications, the class cache will be worth more time than (an also probably cached) image pull)

If you’re deploying Java applications, container size isn’t exactly your first priority anyhow, and this is O(n) additional space.

If image size is a concern, I imagine a native binary using GraalVM would’ve been a better way out anyhow, and you’ll bypass this cache entirely.