Java

1644 readers

8 users here now

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

founded 2 years ago

MODERATORS

Ategon

JackbyDev

thtroyer

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

submitted 2 weeks ago* (last edited 2 weeks ago) by Custodian6718 to c/java

10 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

[–] [email protected] 7 points 2 weeks 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 1 points 1 week ago* (last edited 1 week 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.