record-builder VS Lombok

The problem with this approach is that the people will have to build crutches like https://github.com/Randgalt/record-builder and by the time Java adds missing features all the codebases will be forever polluted with legacy workarounds that nobody will dare to remove because of backwards compatibility.

It also hinders adoption of new features as people will prefer to maintain consistency in their codebases.

Record builder is pretty good for making builders for your Java 17 records

I always have to bring up RecordBuilder simply because of the included Withers and it being a source generator instead of the Lombok weirdness.

The above is not particularly user-friendly. Luckily compiler plugins can provide the missing feature, most notably RecordBuilder:

For records, instead of lombok you can use https://github.com/Randgalt/record-builder which is a valid annotation processor and will not break on JDK changes

In this particular case you can generate the builder with something like https://github.com/Randgalt/record-builder that is both valid java and lombok-like enough

Records + Record Builder or immutables + the trick to hide the implementing class w/sealed are your friend. Both the mutability and naming conventions this generates are vomitus.

Did you use https://github.com/Randgalt/record-builder ?

Try my annotation processor. It generates withers. https://github.com/Randgalt/record-builder

I personally don't use that one much, but you could use this library instead.

Project Lombok has solved that issue of manual boiler-plate getters and setters in Java. If you program regularly in Java it's worth having in your toolbox.

https://projectlombok.org/

Libraries like Lombok can improve development efficiency and reduce boilerplate code. It can greatly reduce boilerplate code by automatically generating getters, setters, constructors, and builders at compile time using annotations.

The above class maps the json data to a java object we can work with. We use Lombok to generate constructors, getters and setters for our code and the Jackson Project to handle serialization and deserialization of json to pojo . We know the response is an array of objects representing the coffee and so above data structure is fit for this.

Almost a decade ago, I started reducing my boilerplate (and saving time with Lombok. It made my life much easier, simple as that. Ever since I've been looking into finding the smoothest solutions for saving time rather than handling all of it myself.

Lombok is a widely used library that simplifies Java code. The @NonNull annotation helps enforce non-null parameters, generating appropriate null checks:

Project Lombok

I gotta agree with /u/rzwitserloot I don't see anything in the lombok repo that indicates they have their "own compiler". I see the "reaching into javac internals" but that's it.

i looked into that and found this: https://github.com/projectlombok/lombok/issues/2310

Funny enough; /u/rzwitserloot is the author of Lombok, one of the most widely used Java libraries in the world. So it's not really some kind of random-ass Redditor they're having a discussion with either.

This removes the need to add the 'Project Lombok' library (and going through a phase of installing it in your Eclipse IDE; old school devs know what I am talking about) and speeds up development time. Java 14 added a new feature of 'Records' which allows you to do the same, but it doesn't offer a 'copy' method to ease your object creation and also enforces the 'final' keyword for variables making them immutable.