Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m coming up with performance goals for the new year, and I thought I’d be fun to put a goal to reduce the size of the code base, especially boilerplate. One action I’ve come up with to address this is to use Project Lombok to make beans as short as they should be. But I have a habit of overlooking downsides to new software and approaches, so I’m relying on the Stack Overflow community: Can anyone tell me why Lombok is a bad idea?
A major downside is IDE support. Since Lombok is not actually a language change, and since your IDE only understands java, you will need an IDE that supports Lombok to get things working right. As of now,
that’s only Eclipsethat includes Eclipse and IntelliJ. If you use eclipse that might be ok, but remember that you are making a decision for future developers as well.I’d suggest you consider moving some of your code into a less ceremonial language such as groovy. We’ve had success moving some of our business logic and models into groovy and it works really smoothly.