Java 22 Release Notes Review - Inside Java Newscast #65
Вставка
- Опубліковано 31 тра 2024
- JDK 22 is set to be released on March 19th! In this episode of the Inside Java Newscast, we will review all the key changes included in this release by going through the release notes of JDK 22.
-- References --
JDK 22 Release notes: jdk.java.net/22/release-notes
JDK 22 Livestream:
- ua-cam.com/users/liveAjjAZsnRXtE
- dev.java/community/java-22-la...
JDK 22 G1/Parallel/Serial GC changes: tschatzl.github.io/2024/02/06...
-- Chapters --
Intro: 0:00
JEPs - Intro: 1:25
JEPs - Final Features: 1:53
JEPs - Preview Features: 4:15
JEPs - Incubator Features: 5:40
New Features: 5:55
Removed Features: 8:55
Deprecated Features: 10:04
Known Issues: 10:49
Resolved Issues: 11:26
Other Updates: 14:03
Performance Updates: 19:55
Security Updates: 25:11
Differences between Oracle JDK Open JDK: 27:23
Outro: 29:01
#Java #Java22 #JDK22 #OpenJDK #InsideJava - Наука та технологія
Java has become the most readable and harmonious language today. Please keep up the good work and listening to the community. Thanks!
Thank you all for your fantastic work. I’m particularly impressed by the ability of this presenter to enthusiastically describe obscure details of changes and fixes - this is quite a feat!
For future Release Notes please add a screenshot or descriptive line of text for every JEP/JDK point. It helps following and allows muted viewing (e.g. in the train).
P.S.: *Please* change the "when" in guard clauses! It's confusing to have a condition for something AFTER the guarded outcome. If you change "when" back to "&&" it reads as part of the same case condition *in front* of the case statement and makes sense again. I want to read left to right! Please consider it.
P.S.S.: The word "case" in switch could be stripped away and it would still make unambiguous sense.
Yea I'll think about that... could just primarily do it as a powerpoint.
I do feed the script I use into UA-cam for the transcript, so you should be able to watch silently and still follow along, and not have to worry about YT badly mangling technical words. Also when referencing a class or VM argument, in the transcript it's the fully qualified class name or the VM argument including decoraters (e.g. --release ...).
The P.S. at this point is definitely *not* going to happen at this point because it would either be a huge breaking change, or create a lot of confusion by allowing both "when" and "&&". I'm not sure if I agree with the reasoning either. As the case labael is still being initially matched on, the "when" is adding an additional qualification for *when* the code block should be executed.
I'm not sure the juice of removing "case" is worth the "squeeze". The goal with a lot of the recent language changes, isn't just about making (Java) code more concise, but also improving readability, and I'm not sure the latter is really being accomplished by removing of the case keyowrd.
@@billykorando6820 Thank you very much for your input! I'm just noticing myself stumbling over the "when", whenever I come across it. The "case" case is rather secondary to me. Thank you as well for bringing the UA-cam subtitle functionality to mind. Good to know that it contains the curated information and not just Google's interpretation of it.
I find it funny that there are still people that don't like the Oxford comma. It's the logical choice and he even made a joke about it haha.
Some people (like me) see commas as indicating a pause in speech, and the pause before “and” can feel awkward.
it is not logical; it is subjective.
Still? Would do you mean by still? It's just wrong, no one should "like" it.
Real charming changes, out of security and performance, most of it out of use for enterprise projects. It's more for small projects or libs that aint gonna change much, at least in my point of view for the time being, maybe in future we'll have much more updated code. I still see and work on implementations that are deprecated or just too antiquated. I hope for the new features like those being more present in courses, tutorials and books.
When can we use the bracket-style index access with strings and maps...☹
Java on UWP, consider both jvm launcher and and a runnable jar application wrapper
They should probably support it officially, but if you really need the feature it's not too hard to make one yourself using JNI. I wrote one for an open source library I'm working on.
how many times you need to write the same native libraries, java@@keithkaranu4258
I love this channel, but the subject of this video is too complicated and to talk about it without proper illustration is a bad idea.
It will be better to show more code snippets or illustrations, just like N. Parlog does.
Kk
Kk
Cacaaaaaaaa
I have posted the new features in Java 22 with working code examples here
ua-cam.com/video/Okju64YVFs0/v-deo.htmlsi=_mxhuCJfnNTL5XOC
First let me understand java 8😂😂
I still need to understand java 8
😂😂😂
Since later versions mostly add features but haven't been taking away features, why not start learning those and let java 8 be java 8
Checkout on @programmingkt
Why does Java release new versions when the world is already moving to Kotlin, and no one is interested in it. The company should stop, admit defeat, and give way to the promising languages Kotlin and Golang. It's a pointless waste of time; nobody starts new projects in this language anymore. Even on TIOBE, it will soon be overtaken by C#. Can someone explain to the creators that their language is no longer needed, they are late in its development, and now they are trying to catch up and convince everyone that Java is still relevant? Heh.
yes, Kotlin does become more popular, but there are still a lot of new projects that are created with Java. Also, a lot of changes that are done for security and optimization are for JVM, so they benefit all JVM languages Kotlin, Scala etc. Yes, Java is trying to catch other languages from behind. Look, if it's easy to replace but not necessary, than it's suited for really large projects since you won't need to do big changes during migrations
In the end, that is the Java promise, backwards compatibility
Problem with java is that its trying to adopt all the lastest goodies but also has to carry decades old baggage to remain backward compatible resulting in a mess of a language
For any new serious project rust is the way to go!!
I am done with java.
I hope you'll have a great time with it and be productive!
Borrow checker vs. garbage collection? I'd say these two languages address different problems ...
I think JAVA should keep on iterating they are on the right track
Yes, backward compatibility can be a problem for well developed languages over many years.
I think language decision makers ought to know when to cancel backward compatibility and kind off kick start the language a fresh with all accrued lessons / good features created over the many years. It is a really tough decision but it can be a good decision to keep the language alive and fresh to new developers while old developers bootstrap new projects with the newest version.
Failure to this really tough decision it becomes less lucrative for new developers to learn the languages as the newer languages start at amazing positions with the right decisions / good features from other older languages.
I use Java and Rust in two completely different scenarios. I like both
@ Yes initial development velocity will be slower in rust (that might change in year or two) but once your code base becomes complex you will be thankfull that borrow checker was all along the way guiding you as a stern instructor to write your code in such a way that would make it easy to maintain and reason about. Also rust with its powerfull enums allow to encode states into the type system itself hence making the overall code way more intuitive and don't get me started on the macros!! they are magic (in a good way)
Can't you be "quiet" just for a couple of years? Too many cooks spoil the broth.
uh... what?
@@nomader5537 Too many releases in two years. Give us a break, please!
Then just stick to the LTS versions. The next one is Java 25 and the cadence is now every 2 years.
ok