Java

1629 readers

1 users here now

For discussing Java, the JVM, languages that run on the JVM, and other related technologies.

founded 2 years ago

MODERATORS

Ategon@programming.dev

JackbyDev@programming.dev

thtroyer@programming.dev

java champions speaking out against lombok (www.linkedin.com)

submitted 1 week ago* (last edited 1 week ago) by Custodian6718@programming.dev to c/java@programming.dev

8 comments fedilink hide all child comments

Java champions and Senior engineers speaking out against lombok

you are viewing a single comment's thread
view the rest of the comments

[–] Lysergid@lemmy.ml 6 points 1 week ago (1 children)

Never had an issue with Lombok. Though I use only getters, setters, constructor and sneaky throws. And I don’t know what exactly they want to debug. It’s literally assignments in most cases. According to such logic, should all reflection based tool be removed too? I guess remove “bad” Spring and JPA/Hinernate then? What a nonsense

[–] Von_Broheim@programming.dev 1 points 3 hours ago* (last edited 3 hours ago)

I thought that the whole point of Lombok is that it's not reflection based, they explicitly refuse to use reflection as a design principle. Afaik lombok statically generates methods and classes at pre compile. That's why for example lombok does not support constructor inheritance or overloading.