Custodian6718@programming.dev to Java@programming.devEnglish · edit-29 months agojava champions speaking out against lombokwww.linkedin.comexternal-linkmessage-square10linkfedilinkarrow-up112arrow-down14file-text
arrow-up18arrow-down1external-linkjava champions speaking out against lombokwww.linkedin.comCustodian6718@programming.dev to Java@programming.devEnglish · edit-29 months agomessage-square10linkfedilinkfile-text
minus-squarestate_electricianlinkfedilinkarrow-up2·9 months agoI never saw a benefit in using Lombok, but I did run into issues with it. As it works outside the compiler, you are basically writing Java+Lombok. And as the article says, with an IDE and a recent JDK there is really no benefit provided by Lombok.
minus-squarestate_electricianlinkfedilinkEnglisharrow-up1arrow-down1·9 months agoI disagree. It looks leaner. But the code is still there and because it’s invisible, it requires you to remember more.
I never saw a benefit in using Lombok, but I did run into issues with it. As it works outside the compiler, you are basically writing Java+Lombok. And as the article says, with an IDE and a recent JDK there is really no benefit provided by Lombok.
Its just leaner:)
I disagree. It looks leaner. But the code is still there and because it’s invisible, it requires you to remember more.