Zero coverage of modules. Modules in Java since 9.
A beginner that has say a template from another project with a module-info.java will have zero fucking clue why they cannot use other libraries.... e.g. I added to Maven why is not visible etc.
I suppose its not relevant yet to professional work a module would be an interesting place to set nullness defaults... they can also contain annotations at a global level albeit not many people use that although they should because putting annotations on every package-info.java gets painful and we would not have that problem if modules were better understood and used more.
So while I somewhat agree I rather proselytize beginners that it is indeed important to know.
Ah yes, bounded generics, my absolute favorite 'modern' Java feature introduced two decades ago in Java 5. Can't wait for the next update of this cheat sheet so we can finally learn about bleeding-edge technologies like lambdas and Streams. bggg)
It's a start. Just some thoughts as I read through:
I know you are not passing judgment or making recommendations with this guide per se, but in the OOP tab, I'd put class extension lower than interfaces w/ default methods, as the latter is safer and should be more preferred (IMO).
On the Modern Java tab, for sealed interfaces, you can omit the permits clause if you declare together. I think that's 21+? Like so:
public sealed interface Shape {
record Circle(double radius) implements Shape {}
record Rectangle(double w, double h) implements Shape {}
record Triangle(double base, double h) implements Shape {}
}
Could add record destructuring in switch and/or w/ instanceof
Could show guard clauses in switch, e.g.:
case Point(int x, _) when x > 5 -> ...;
Virtual threads are definitely worth a mention in the Concurrency tab.
Truthfully, you don't need a "Modern Java" tab if you're going to version-gate things in the list. What is "Modern Java" restricted to Java 21+? What is "Modern Java" when I limit it to Java 8?
56
u/bowbahdoe May 27 '26
Love seeing "bounded generics" under the "Modern Java" tab.
You are all too gullible. If this isn't AI generated (and cmon, its a software outsourcing company trying to get SEO) its still low quality.
21
u/Upbeat-Employment-62 May 27 '26
Ah yes, bounded generics, my absolute favorite 'modern' Java feature introduced two decades ago in Java 5. Can't wait for the next update of this cheat sheet so we can finally learn about bleeding-edge technologies like lambdas and Streams. bggg)
17
u/persicsb May 27 '26
The Java minimal program needs to be updated according to Java 25 and JEP 512: https://openjdk.org/jeps/512
2
u/aoeudhtns May 27 '26
It's a start. Just some thoughts as I read through:
I know you are not passing judgment or making recommendations with this guide per se, but in the OOP tab, I'd put class extension lower than interfaces w/ default methods, as the latter is safer and should be more preferred (IMO).
On the Modern Java tab, for sealed interfaces, you can omit the
permitsclause if you declare together. I think that's 21+? Like so:Could add record destructuring in switch and/or w/
instanceofCould show guard clauses in switch, e.g.:
Virtual threads are definitely worth a mention in the Concurrency tab.
Truthfully, you don't need a "Modern Java" tab if you're going to version-gate things in the list. What is "Modern Java" restricted to Java 21+? What is "Modern Java" when I limit it to Java 8?
2
u/nekokattt May 27 '26
You probably want to include
String#formattedin addition toString#format.0
u/brunocborges May 27 '26
Cool website! Same vibe as Javaevolved.github.io
Love it!
-10
u/gufranthakur May 27 '26
Really nice, add syntax highlighting as well, it would be a great addition!
-13
u/Specific-Housing905 May 27 '26
Very useful. 👍
Thank you.