Modern Java in Action

[@TheBigLou13]

20:00 I would be interested in a dedicated video to these reflection capabilities. Great talk/presentation, showing a lot of the new features in a connected way while also giving some additional information about them and their usages/options/capabilites/benefits!

[@nipafx]

That dedicated video is not a bad idea, I'll put it on the list. 😊 If you want to look into it yourself, check out Class::getRecordComponents: docs.oracle.com/en/java/javase/21/docs/api/java.base/java/lang/Class.html#getRecordComponents()

[@dmitriimoldavanov4701]

36:04 Pretty.pageList -> what if page is null? Should we put additional check for that?

[@nipafx]

You can just add a `case null ->` to the switch if you want to handle that case. Otherwise the switch will throw a NullPointerException.

[@jfkwasnoscope]

Good talk Nicolai, love the frequent uploads on the channel.

[@prdoyle]

30:42 - RIP string templates

[@javaRelated]

Thanks Nicolai, Great Talk as expected.

[@nipafx]

Thank you!

[@c00ckiez]

Banger video, love coding sessions like this. Keep it up!

[@gioeffectpro]

How is your intelij idea so smooth?

[@asd-xr9ii]

Great, thanks!

[@ihor_1995]

Great video! Thanks, Nicolai!

[@BrazenNL]

12:10 `git eradicate`?

[@nipafx]

I'll have to look up the exact alias, but what it does is revert all changes and delete all untracked files.

[@BrazenNL]

@@nipafx Oh, right, an alias. 🤦

[@stefumies]

Great presentation, and what a lovley theme, what is it and which font?`Its crisp and clear

[@muzzletov]

i used ktor for that exact purpose. i feel like, oracle took a lot of inspiration from kotlin.

[@edgardcz]

KUDOS! Awesome presentation! and remarkable job from the Java team! Please guys, bring the null check with ? and something similar to elvis operator to the lenguage!

[@andmal8]

Thank you!

[@octaviantheodor]

Super lovely, thanks! But "abusive," indeed :) Imagine handling a new type of GH page... How many switch-es were there?

[@nipafx]

That's not the abusive part, though. 😉 If every switch were instead a method on `Page`, adding a new type of pages requires you to implement all operations. If `Page` used the visitor pattern, adding a new type of pages requires you to update all visitors (i.e. operations). Here, adding a new type of pages requires you to update all switches (i.e. operations). There's no escape from this (unless you want some operations to execute a default action for all new types that are ever added).

[@octaviantheodor]

Fair enough :)

[@NineInchTyrone]

Is Java modern COBOL ?

[@prdoyle]

Great talk! Editor - looking at Nicolai is cool and all, but you need to keep showing the code or we can't follow along.

[@nipafx]

I agree! But the video was edited live at Jfokus (for their live stream) as you see it here and we don't have access to the original source files to re-edit. 🫤

[@hba6018]

30:42 Beautiful String Templates that were not appreciated.

[@nuclearscissors]

Great talk! Loved the structured concurrency bit, pattern matching (blew my mind a few times in the talk with how awesome the code looks with it), string templates and other new features overall. Java 21 has really upped it's game in terms of neat tricks that make the life easier.

[@hoo5886]

awesome

[@ambrozykleks626]

good job, friend

[@yonishachar1887]

22:26 - I hate when tutorials show how to do stuff and then say "super simplified", what exactly is simplified here?

[@nipafx]

I go into it a bit starting at 22:00: You can configure all kinds of request settings and you can briefly see a few options in the popup at 22:08. So "simplified" in the sense that this specific project needed no extra configuration because the defaults all work - something that may not be the case in a real-world application.

[@yonishachar1887]

​@@nipafx Thanks a lot for the explanation. I'm interested to know what would a real-world application configure as well besides Proxy if it's a web scraper.

[@nipafx]

@@yonishachar1887 That all depends on the application, where it's connecting from, and to what. I would recommend to start with the defaults and when something doesn't work as required, analyze why, then find the setting that tackles that (e.g. connection timeouts, cookie policy, or a differently-sized thread pool).

[@rahulvijay1781]

I have 1yr of experience as a java developer..after i see this video makes me think i am a joke 🤡

[@nipafx]

Don't think that. A year of experience is a great point to be productive and to really start to understand the language and its ecosystem. Stick with it! And keep in mind that the talk was prepared and rehearsed with the express goal to make the code look good.

[@JamesStansell]

Everyone has to start somewhere! One thing about programming is that there is always more to learn ⭐

[@rahulvijay1781]

Thankyou guys it means a lot ♥️

[@thiagogeisler8715]

@@nipafx Hello, Nicolai. You could consider taking the JAVA team to open a project to research a deterministic memory management system to be used by developers who need low memory consumption and develop real-time systems. I have seen some languages ​​that have adopted deterministic memory management, such as MOJO, Rust, Swift, and NIM. Nim, for example, adopts a system called ORC. It's just that some of us didn't want to have to leave this wonderful JAVA ecosystem for any other language, not even temporarily to make system-level applications.

[@silentprotagonist3786]

​@@nipafx I just started learning Java seriously a week ago and this lowkey gives me hope 😹

[@DamLee88]

great!

[@badpotato]

nice viewo

[@iogilarb]

Haa... Java

[@jfkwasnoscope]

The string interpolation is still super ugly and should be replaced and yes I read the explanation for this incredibly unpractical and ugly design in the jep. It's not just a "small amount of convenience" that we're missing out on.

[@AnimatedV]

These highly professional people have no concept of quality screencasts, do they? The wastage of time in Java community is like no other. Untangling complexities too remains elusive.

[@krellin]

records immutable = bad copyOf just to make immutable list = bad we had better solutions for all of this long time ago

[@avalagum7957]

Could you please tell us what, you think, is better?

[@krellin]

@@avalagum7957 sure, records forcing you immutability is bad because for most it means boilerplate code, shit performance (no resue from cpu caches after you mutate) lots of garbage (which is less of a problem, cos gcs are very good these days)... what they should have done is give you options, if you want immutable declare your fields as val or var like kotlin... immutability is very niche technique that mostly library devs should use not general public... good example is string, more good examples? hard to come by

[@krellin]

@@avalagum7957 copyOF sucks, because it actually will copy unless underlying was immutable already... instead kotlin solved it better yet again... List = Immutable version, no mutator methods, MutalbeList = MutableVersion.... You can simply return List even though underlying is mutable (so you do a free downcast)... and if a developer goes out of his way to cast it back to mutable and mutate it then its his problem... Again they are lazy and dont do the work even though jetbrains showed them years ago how its done properly.

[@krellin]

@@avalagum7957 if records were some sort of C type data structures packed in memory i would understand immutability, because you cannot predict length of some fields to count pointers... but all it does is forces you to use immutable pojos... why tf would you force it, i dont know... My only guess is laziness + since they are in the a cloud provider club, they do not want you to write efficient software that does more with less... This code looks like shit, and i didnt watch further. As a java dev it pisses me off that they make short sighted decisions to hit their 6 month schedule, even when good tested solutions to these problems are already out there for many years.

[@cosmowanda6460]

​@@krellinyou're right, records force immutability. But isn't that what they were created for? If you want to modify your classes everytime, then records are clearly not what you should use. If the jvm works like any other language though, anything that's immutable should help the compiler make more optimization. val and var isn't the good example you think it is. They could have used literally any other names that didn't look so identical. If I remember Kotlin correctly, its concept of immutability is also similar to java in that the reference is still mutable. So val in Kotlin, is really just final in java.