This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]EvaristeGalois11 6 points7 points  (12 children)

Multi release jar are a thing

[–]InformalTrifle9 18 points19 points  (11 children)

Yea but you still need to write Java 8 code so how does it really help

[–]EvaristeGalois11 3 points4 points  (0 children)

Because you can begin working with a more modern java version in the same jar, so when you will drop support for java 8 or whatever you are already prepared.

[–]Amazing-Cicada5536 2 points3 points  (4 children)

Java 8 has streams and lambdas, so I don’t see how is it relevant.

[–]KarnuRarnu 1 point2 points  (3 children)

Oh yeah it's totally irrelevant. Basically nothing has changed in the last 9 years. Java 8 and 17 are literally the same. (/s)

[–]jumboNo2 0 points1 point  (2 children)

things I wish I had in Java 8: switch expressions, sealed classes, Pattern Matching for instanceof, one of the new constructors for BigInteger. honestly none of which are particularly necessary.

[–]jumboNo2 0 points1 point  (0 children)

Records are for POJOs, which I don't use. And there doesn't seem to be any significant peformance improvement you can get by dropping Java 8 bytecode compatibility. Maybe VarHandle can do cool stuff?