Custodian6718@programming.dev to Java@programming.devEnglish · edit-21 year agojava champions speaking out against lombokwww.linkedin.comexternal-linkmessage-square6linkfedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1external-linkjava champions speaking out against lombokwww.linkedin.comCustodian6718@programming.dev to Java@programming.devEnglish · edit-21 year agomessage-square6linkfedilinkfile-text
minus-squarestate_electrician@discuss.tchncs.delinkfedilinkarrow-up0·1 year 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_electrician@discuss.tchncs.delinkfedilinkEnglisharrow-up1·1 year 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.