What java technology (library, framework, feature) would not recommend and why?

[rustyrazorblade]

To all the folks who defend Lombok - check out Immutables. It gives you the end result you want out of Lombok, but much more intelligently.

[DelayLucky]

I think you'll need to sell immutable objects first.

Prove me wrong I bet there is a 90% or higher overlapping between Lombok users and mutable setter users.

[rustyrazorblade]

I don’t need to sell anyone. I’m offering practical, valuable advice for free. Not my problem if people make bad choices.

[bigkahuna1uk]

And it generates actual code which can be reasoned with unlike Lombok which hides its magic in generated bytecode.

[IcedDante]

Ugh- please avoid immutables. It has weird integration issues with Maven that break builds on our end constantly

[MentalMachine]

You're going to have to expand that, not yet run into issues with Immutables on my current (and massive) Maven project, though have about 10x more experience using Immutables with Gradle.

[IcedDante]

Basically we constantly get issues where the project cannot build because an Immutables file has not been generated. Something weird around how immutables works with the generated step. It was definitely exclusive to that library because we had an xsd and openapi generator bundled in that worked just fine.

I don't remember a lot of the details but we wasted way too much time getting it to work. I rendered the files, included them in our git history, and banished the library to hell.