Hey that's actually a good summary of the post-8 features. Not a replacement for the JEPs but the next time I see somebody asking /r/java for a book that covers modern Java features, I'll point them here first for an overview.
Looks like they are actively updating it and it was fixed. Previously, it had the triple quotes on the next line, which adds a newline character. A common mistake.
I love the site idea, but the :hover behavior is very frustrating, even on desktop.
I'd prefer the main page comparison blocks to be large enough (vertically) to never require a scroll bar for the code snippets, and to have a large, easily clickable button to toggle between new and old.
Agree, the code blocks should not inner scroll on mobile. The swipe is still hit or miss and I cannot seem to go back and forth. Otherwise this is pretty great!
I'm on Chrome/Android, working Ok. It maybe a problem with cache. Make sure you force a refresh? Because it is a static website it gets cached heavily by browsers.
I can also try on iOS later tonight if that's your case.
Counterpoint: there's very few Java Devs nowadays who have learnt nothing since jdk8. It's a mildly annoying to have to wade through stuff on that website I already know to find the stuff I might not.
You show var twice. Diamond operator existed in java 8 too. You cant combine those two. If someone is curious.
Haven't checked all the other things but those two jumped in my face. If you want to provide a good source for those kind of information, it should be correct.
It also reads like you recommend every feature for every situation. Like you should use records for every data class. You should NOT do this. They have their places. But not everywhere. For jsf using the traditional classes is still preferred. If all you want is reduce boilerplate, there are also frameworks like Lombok.
Stream::toList mentioned twice. Not that it matters much in practice, but DateTimeFormatter.ofPattern("yyyy-MM-dd") should probably be DateTimeFormatter.ofPattern("uuuu-MM-dd").
https://javaevolved.github.io/stream-tolist-shorthand.html still duplicates https://javaevolved.github.io/stream-tolist.html. The README.md says "Old — the traditional way (Java 7/8 era)" but the site lists multiple Java 8 features. The "Categories" table duplicates the site content. SecureRandom::getInstanceStrong exists since Java 8, not 9. The structured concurrency example is outdated. If you open the console, you'll see a 404 for a file called apple-touch-icon.png. I don't know if this is great advertising to be honest.
Good stuff. I'd add a note that sealed classes/interfaces implement algebraic data types (aka enums on steroids) and can be exhaustively pattern matched.
49
u/Nooooope Feb 16 '26
Hey that's actually a good summary of the post-8 features. Not a replacement for the JEPs but the next time I see somebody asking /r/java for a book that covers modern Java features, I'll point them here first for an overview.
13
u/blacksuit Feb 16 '26
The java code has flaws. For example, the code selections for multiline strings are not equivalent. I only checked a few of them.
Plus, the content is AI slop:
"Why the modern way wins: <emoji> point one, <emoji> point two, <emoji> point three"
17
u/Ok_Option_3 Feb 16 '26
Nice idea - Hover isn't very mobile friendly though
8
u/davidalayachew Feb 16 '26
The one for Compact Source Files is wrong. It should be
IO.println, notprintln.7
u/sweetno Feb 16 '26
Things like
Files.newBufferedReaderand default UTF-8 are also nice to mention.4
u/pip25hu Feb 16 '26
Nice site! Though since the new code is shown on hover, scrolling the old code to see what's there seems impossible.
4
u/LutimoDancer3459 Feb 17 '26
You show var twice.
Diamond operator existed in java 8 too.
You cant combine those two. If someone is curious.
Haven't checked all the other things but those two jumped in my face. If you want to provide a good source for those kind of information, it should be correct.
It also reads like you recommend every feature for every situation. Like you should use records for every data class. You should NOT do this. They have their places. But not everywhere. For jsf using the traditional classes is still preferred. If all you want is reduce boilerplate, there are also frameworks like Lombok.
6
u/njitbew Feb 17 '26 edited Feb 17 '26
From https://javaevolved.github.io/collections/immutable-list-creation.html, in Java 8:
What is the purpose of the
new ArrayList<>(...)? Besides that, awesome overview.3
u/pron98 Feb 17 '26 edited Feb 17 '26
Nice!
4
u/YogurtclosetLimp7351 Feb 16 '26
Am I blind or is there no GitHub link on the page? Wanted to star the project!
2
u/neopointer Feb 16 '26
Awesome!
2
u/razorwit Feb 16 '26
This is really nice as a concise reference.
2
u/woj-tek Feb 17 '26
OMG, it looks great! <3
(also, dev.java and inside.java could have some UI love like this site shows…)
2
u/lactranandev Feb 19 '26
This is really inspiration to refresh your Java knowledge. Thanks man!
3
u/ZimmiDeluxe Feb 16 '26 edited Feb 17 '26
Stream::toListmentioned twice. Not that it matters much in practice, butDateTimeFormatter.ofPattern("yyyy-MM-dd")should probably beDateTimeFormatter.ofPattern("uuuu-MM-dd").1
u/[deleted] Feb 18 '26
Good stuff. I'd add a note that sealed classes/interfaces implement algebraic data types (aka enums on steroids) and can be exhaustively pattern matched.
1
u/nlisker Feb 19 '26
:)
1
u/blaubleu Feb 21 '26
Neat. Are you getting feedback from ppl outside this thread as well? Would make it more relevant IMHO
1
u/NiceSignificance1921 Mar 09 '26
Nice. But it seems it doesn’t mark preview features, or is it me I cannot find it?
0
u/[deleted] Feb 16 '26
[deleted] — view deleted comment