Thanks for your comment! I totally agree with you, and as soon as I published this post, I regret not explaining the cons of using this library. Since Java 14, they are making a considerable effort by making java less verbose, and using Lombok to those newer versions isn't helpful as most people think.
I never had a problem using it, but I heard people getting into trouble and saying that it's not easy to debug an application with Lombok.
Who knows if someday they're going to make a great library that has no tradeoffs, right?
Shai Almog
Yak Barber, duck whisperer, hunter of bugs, feeder of dogs, heap climber, stack explorer and rider of shells
Nicely written. I like Lombok and use it a lot but I'd like to point out a couple of things:
Newer versions of Java have records and var keyword built in. That's probably the better approach long term. If you target the current LTS (Java 17) then you should be pretty good and Lombok isn't as helpful.
Some people claim Lombok causes problems. I've never run into it but I think these stem from the fact that Lombok generates hashcode and equals methods by default for some annotations. These can conflict with entity tags in JPA.