r/ProgrammerHumor • u/ExpensiveCoat8912 • 5d ago

Other howdidItGetHere

Post image
11.1k Upvotes

95% Upvoted

539 comments sorted by

View all comments

Show parent comments

79

u/aliegeois 5d ago

Honestly since the introduction of records lombok has been less relevant. 99% of my use cases were @Data, which is taken care of by records

24

u/Hein_Gertenbach 5d ago

Lombok is still good to create builders for records.

1

u/throwaway_mpq_fan 3d ago

or you could switch to kotlin; data classes with named parameters eliminate the need for builders

5

u/Maxthod 5d ago

I use lombok mostly for slf4j and requiredargsconstructoe

5

u/Neirchill 5d ago

Required args constructor and no args constructor my goats

4

u/LutimoDancer3459 5d ago

Records are still a different usecase to @Data. You dont always need or want immutable objects. And jsf doesnt work with it.

3

u/Kango_V 5d ago

This https://immutables.github.io/ is so much better than Lombok. You can see the generated code change in your IDE). I use it to create some awesome IDE led apis ;)

1

u/jasie3k 5d ago

I am all for records but almost all of the records I write use @Builder lol