Records In Java - Full Tutorial - The Best New Java Feature You're Not Using

thanks

Why is my Java professor not teaching this?!

This video reminds me so much of the mCoding video on python Data classes!

DOES RECORD WORK WITH SPRING BOOT?

Records are a stupid implementation. Enough said

It would've been even better if record implemented builder pattern. When you have a lot of fields, working with all feilds constructor looks like antipattern

Very well explained. Thank you kindly.

Great video! Question please: How did you generate the toString method quickly without the IDE generation tool?

Interesting but when i look at it my classes often have some value which can change. Consider putting employee address in the employee record but people can move. People can even change their names.

You are perfect 👌

If you suffered from writing POJO classes throughout the years then you will appreciate Records and what they can do for you? Cuts down on lots of redundant boilerplate code...

Can we use records as a DTO that will be mapped when a request comes in?

Java at this point feels like 40 year old man that tries to stay young by adding cool new stuff to its life. Good content tho :D

Nice and precise explanation without any fuzz 🎉

Thanks you, could you make a tuto about permits keywords?

creative bor👍👍

It is basically a Kotlin Data class for anyone wondering what Kotlin’s equivalent is before watching

That's a really good teaching... Thanks 🎉

Hi great video.
we use lombok a lot in our projects and the record seems less efficient in comparison. I am wondering what you guys think about it.

I check out ur course... But as a Indian citizen I found it some what expensive..😅

Thank you brother!

@Lombok has entered the chat.

Kotlin data class...

well explained as usual !

Interesting feature well explained thank you.

Can we use records in spring data jpa for data crud operations?

Very informative 👏

I find it weird that properties of a record is still private.
Since it's `final`, shouldn't it be okay to just have the properties public instead of retrieving its value through a function? Would look way cleaner too.

Thanks you!!

Huh, isn't this just a kotlin data class?

Equivalent to a 'data class' in Kotlin.

The more important implements would be the Comparable interface to ensure a compareTo method for sorting.

Adding records to Java, takes me back to the 1980s.

great video, thank you!

why didn't my cs teacher tell me about this

what if we have more number of fields in data class lets say 100 fields, in that case records looks very bad ....what is your input?

For what purpose someone will need the object full of constants? For me it sounds a bit useless?

Thanks a bunch

Very useful.

is it possible to overload the constructor with less parameters like public E (String name) {…}?

cool

Doesn't name.toUpperCase() mutate final name field?

Hello john , can you please make a video on Heap sort ?

Beautiful video 💚 thank you 😊

awesome!

What happens if you have a telephone field? Telephone numbers change from time to time, would you have to make a regular class instead of a record?

Great tutorial

Records as an entity or json rendering?

Guitars 🎸, drums 🥁, and programming. 💻 Yep! You're definitely part of my tribe. Excellent video! Keep it up.