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.
Hi, Mati. I liked the video. It's very clear. Could you please explain better why you avoid using Lombok?
Hi, thanks for the comment! I will make a follow up video about what I think about Lombok
New sub! Nice info, thanks for sharing
Thanks for subscribing and the kind comment!
Very cool. Looks like Kotlin
Yes it does!
A small inaccuracy... records haven introduced in JDK 14 as preview feature and finalized in JDK 16...
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.
Thanks for the comment! I’m preparing a new video on way I’ve started to avoid Lombok
The learning gap between Java and kotlin is getting smaller and smaller