Records: Data classes in Java | Bye Lombok? | Explanation + Tutorial

In this episode we look at Records in Java, introduced in Java 14.
How to use records, the amazing advantages and what are their limitations.
Follow me!
- Twitter: / progwithmati
- LinkedIn: / matiasdsalerno
- GitHub: github.com/Programming-with-Mati

[@dehorian_stories]

New sub! Nice info, thanks for sharing

[@programmingwithmati]

Thanks for subscribing and the kind comment!

[@gustavolobos3653]

Hi, Mati. I liked the video. It's very clear. Could you please explain better why you avoid using Lombok?

[@programmingwithmati]

Hi, thanks for the comment! I will make a follow up video about what I think about Lombok

[@khmarbaise]

A small inaccuracy... records haven introduced in JDK 14 as preview feature and finalized in JDK 16...

[@guilhermemelo3760]

Very cool. Looks like Kotlin

[@programmingwithmati]

Yes it does!

[@ronySky_]

That's a good introduction to Records, but you don't really say why you think this is better than Lombok. Not only moving away from classes you lose the powers of inheritance, but without Lombok you lose builders, which are awesome if you're dealing with models with many fields.
Not to mention records' alternative to overriding equals/hashcode when not using all fields is much more verbose than using Lombok annotations.

[@programmingwithmati]

Thanks for the comment! I’m preparing a new video on way I’ve started to avoid Lombok

[@nanonkay5669]

The learning gap between Java and kotlin is getting smaller and smaller