3 ms·
Ugh Lombok! Literally everything it does is replaced by any competent IDE with auto-generated methods, with the added benefit of not requiring special build ha
by jameslars 3y ago
Ugh Lombok! Literally everything it does is replaced by any competent IDE with auto-generated methods, with the added benefit of not requiring special build handling steps because the library can't play by the normal annotation processing rules.
There was maybe a time Lombok made sense. It does not anymore. Death to Lombok.
- never_inline 3y agoThat's usually one time concern. Much better than having boilerplate lying around IMO.
- nabogh 3y agoDisagree. Just because the ide wrote a bunch of boilerplate for me at some point doesn't mean I can know the boilerplate is unchanged without reading a bunch of getters and setters. The mental burden of tiny classes is so much nicer to read.
- jameslars 3y agoThis is every Lombok lover's favorite strawman argument I've run into. I've been coding in Java professionally for ~20 years. I can count with zero hands the number of times I've been burned by a getter or setter getting changed into something surprising. If you really need auto-generated getters/setters/builders - Immutables [1] is a library that does it using bog standard annotation processing rules that don't require hacking your build process. [1] https://github.com/immutables/immutables https://github.com/immutables/immutables