A couple of years ago, I had a dev introduce Lombok into some code without me knowing. That let me be a classic naive user.
The result was total confusion on my part. Sooo much code was being automagically generated that I couldn't figure out the code and spent a lot of time chasing my tail and very little time looking at the crux of the code. My own personal preference is either - use a language like Julia if you want magic. It's fantastic and all to have amazing stuff and coders expect to see it. - use an IDE to generate the boiler plate and put it into its own little annex in the code with the interesting bits near the top of classes. That lets debuggers and IDEs that don't understand Lombok to function without impairing readability much. Concurrent with that, use discipline to not do strange things like changing the expected meaning of the boilerplate. That's my preference, but I wouldn't want to push that preference very hard. My own prioritization is on readability of the code by outsiders. On Fri, Jan 21, 2022 at 2:25 AM James Turton <[email protected]> wrote: > Hi again Devs > > This one is simple to describe. Lombok entered the Drill code base this > year, but not everyone feels that Lombok is appropriate for every code > base. To my, fairly limited, understanding the advantage of Lombok is > that boilerplate code is reduced while the disadvantage is the > deployment of code generation magic that can have untoward effects on > build-time tools and IDEs. > > So here is a chance to opine on Lombok if you'd like to. My own opinion > is very near neutral and goes something like "It burned me a bit once, > but hasn't since, and less boilerplate is nice. I guess it can stay > <shrug>. I hope I don't regret this one day." > > Regards > James >
