[JulianMorrison]

Speaking from personal experience, the creators of most of the recent JDK versions have made very poor efforts to explain the changes, it's mostly just a list of RFC type documents, and who has time?

An example of something that compares favourably would be Go, where they always blog about the changes, and there's easy to find official language documentation (and not just autogenerated API docs).

[kaba0]

Have you tried for example the linked article with all the JEPs listed with lengthy descriptions? And with links to relevant mailing lists if it didn’t satisfy your curiosity?

[JulianMorrison]

I just yesterday took the time to go and read through them. And I still consider it awful UI.

- A list of links is not a summary. The list is too short, reading every individual linked document is too long. The format of JEPs tends to bury the lede. As such it feels like wading through mud.

- Changes that affect the programmer experience are mixed at random with changes that affect internal details of the implementation.

- Changes that introduce experimental features are mixed at random with changes that are final.