To Lombok or not to Lombok
I have recently had some perspective on Lombok; a code generation library for Java. I am sure alternatives exist in Java and other languages. I am not going to go into the inner workings of these libraries, more the pros and cons of delegating boiler...
Responses
Markdown supported · ⌘↵ to post
Great post on an important subject!
I think you meant to put
Lower barrier to entryin the pros and not the cons?I'm generally in the pro Lombok camp for Java 11 apps. With newer code I will probably use records. Didn't get a chance to "really" build non-test code for the more modern version yet as I'm too busy with "real" code.
The one big complaint I hear from people on Lombok is that of reliability. That things fail "oddly". I think most of this tracks down to Lomboks implicit hashcode and equals implementations in most annotations. These conflict sometimes with caching and JPA due to problematic state changes.
If we're aware of these problems I think Lombok is pretty cool. But if I'll start a new project now I'll probably target 17 which makes it less useful.