Fantastic

Awesome talk overall and great short and practical recaps of the most fundamental changes in the recent Java versions. I went ahead and featured it in the latest issue of Tech Talks Weekly newsletter 🎉! With that said, I must say I like that Java finally introduces battle-tested concepts long-time present in other languages. Algebraic Data Types enabled by sealed classes and records along with record patterns (new addition in Java 22) are a powerful tool for domain modeling.

Natan produced many great talks so far and this one is not different. This talk has been featured in the latest issue of Tech Talks Weekly newsletter. Congrats 👏!

Some people can never be helped 😅🤣

does it work with java21 though?

I thought this was gonna be interesting... meh.

1:07:55 :) `Boolean::booleanValue`

Great talk, very interesting seeing folks being explicit about the challenges of event sourcing. Still curious tho, what happens to the message if the machine/pod/volume disappears before successfully producing/uploading to S3, and after accepting the database write?

I jumped from java 8 to 22 😂. Now I'm willing to stick to 22. Now bring derived records and I'm 100% in.

Well done guys! Great presentation 😃

To be honest, I would have put product and inventory in the same db 😅

What’s the point of uploading a talk with no full screen or presentation screen?

Worst keynote ever

Nice

I learned a lot. Thank you.

That story about the new framework while on the finishing line always cracks me up.

Ted is one of the speakers who you can listen to because of his style to keep audience engaged with anecdotes.

Please provide the whole workflow I want to create my own product out of it.

Always good to listen to you Ted, you always hit the point, I feel motivated after listening you

Is zgc and c4 99% the same?

such a good presentation.

amazing!!!

Marvelous talk, well explained and informative. Thank you!

maybe i'm wrong, enlightn me. so in the nutshell all the middleman does nothing and lets give it all to the developers. coz scrum too easy, lets add more meeting and longer coz too many people will asking, and do less coding, lets the code bam... code it's self, lets make this new dogmatic? wasn't the whole idea of splitting and putting middleman to make the workload splited as well, some people do this and some do that and thus deploying an app seem faster than waterfall, even if it's with iterations. if so why the need of middleman. and if the code can write it's self why we need developer anyway.:)

high peak of java 33:38

I kind of missed why would someone want to run wasm on server side?

This video is not about LLM-powered application. It seems to be the wrong video

why are watching java 22 when world is using 8 and 11

Any slides for this video? The video was fairly blurry and hard to read.

So many useless features that just complicate the language for no reason. So much wasted energy that could have gone into useful things, such as async/await, or dynamic hardware thread use via hill-climbing, or better security features like flags to disable entirely certain unsafe features in all dependencies, etc. Java is lost in a sea of design-by-committee decisions.

That stupid projector… (or cable, I know).

Virtual Threads in Java are such a terrible implementation. I wonder why they didn't look at other languages first.

Does anyone know which editor he's using?

Hi so can we extract nested pojo from the string we pass in AiServices

Amazing presentation.

It is worth of time,

How to handle pressure in the Scrum Sprints as a Java Developer

5:10 Ngl, i am a little bit conused.. reorder() exists as sort(), duplicateConsecutive() exists with distinct(), groupdUsing() exists through collect() and of course mapConcurrent() exists trhough map(). Yes.. you have to do some extra stuff instead of just putting a your lambda operation as argument but... it exists. All of that would be just another method name or syntax.

Getting Runtime error is more fun than getting compilation error ..

My knowledge is still somewhere at Java 8 level. I am on the way to JDK 21+. That was a good start. Thank you, Joe.

Simon's talk has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats!

That was a very good talk, enjoyed it very much and a crucial point was very well presented (use APIs to access the "db owning" service). I have mixed feelings and experience with the monorepo approach. It sounds good, it has some benefits. But still, in reality it mixes concerns (deployment and code sharing) imho. I have seen it being misused to "share" common configurations of services and a lot of other weird stuff. Then the discussion about build times and instant feedback which leads to a lot of effort going into differential build complexity. There is no such thing as a free lunch... or: it depends 🙂

Hey Devoxx, Thanks for sharing this cool stuff! Unfortunately I can't use the same library for form validation in my development environment due to strict policies restricting the use of third party packages and software. But when I use only the directive I get an error: NG0100: Expression has changed after it was checked. Please advise who knows how to fix them for nested elements that are added and removed by condition.

There's something off with the sound, it'd be great to fix this.

I will say, json frameworks can respect rpivacy and use constructors or factory methods if you tell the library where to look

Very good for sure

Victor was so were so fast in dismissing FOR over stream, saying of course stream. Have you ever heard this saying "Those that fails to learn the lessons of the past are doomed to repeat them!" Why would you want a non performant alternative, lack of identation, hardy readable alternative over FOR? So what is that boiler plate so troublesome that we need having 1 line of code instead of 5? Is that FOR so annoying that we are willing to sacrifice performance and clarity over it? What about using fewer objects across multiple classe instead of multiple objects in a single class? Do you want multiple entities in database too? What about performance (who cares, as long as it is OOP and it looks nice we don't care about performance right?) ? What about erasing the middle man? If you are so keen in erasing the middle man, why don't you call the repository directly from the controller? Why use the middle man "Service" ?

Nick Tune is a genius!

C64 has great back the in days :-)

Java is a Code Smell.