Some checks are applied, but I don't know the details. In effect, crafting a malicious cache is similar to crafting a malicious JAR (although more technically challenging).

A speaker never recommends too much, nor too little, he recommends precisely as much as he means to.

"Need" is a strong word, but I think it would be beneficial, yeah. I'm not sure about the default severity, yet. The community should gather a bit more experience with this feature before stronly recommending it.

Lol. All good. :)

"Amber & Valhalla - Incremental Design and Feature Arcs"

Spotify: open.spotify.com/episode/5Ubm...
Apple Podcasts: podcasts.apple.com/de/podcast/a...
Podchaser: www.podchaser.com/podcasts/ins...
YouTube: www.youtube.com/watch?v=guuO...

Thanks for watching, folks! If you're interested in the Wikiemdiae event stream demo (in simplified form), see this gist: gist.github.com/nipafx/bb980...

We made a similar video series two years ago (youtube.com/playlist?lis...) and were already shooting it when I made the original "Java 21 is no LTS version" video (youtu.be/3bfR22iv8Pc?...). There was no change of mind - it's just an insistence of using the right words for the right things.

But I never argued that LTS isn't important. Yes, I think most people slightly overvalue it and more projects could run the current JDK but that doesn't mean LTS isn't an important part of the ecosystem - it clearly is. It just isn't an attribute of "Java $version" and that's all that video says.

Yes! Bonus points if you bring enough to share. 😉

I'd say you did. That video[*] explains why "Java 21/25 is an LTS verison" is a non-sensical statement (because support is not applied to Java versions but to JDK distributions). It doesn't comment on the importance of LTS.

[*] script: nipafx.dev/inside-java-...

The pithy answer would be "citation needed", hinting at the fact that I never once said that.

We're discussing 21 -> 25 because that will be the jump most projects make.