record-builder VS awesome-annotation-processing

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

- Checker Framework

There's quite a list here https://github.com/gunnarmorling/awesome-annotation-processi... (Though I don't think Error Prone is actually an annotation processor, but rather a javac plugin.)

There's some irony in that Immutables and Autovalue are often named as alternatives for people that dislike Lombok's implementation but do like (some of) Lombok's features.

The documentation could be less sparse. I found the following Awesome Java Annotation Processing. Here's a simplified class diagram to get you started:

Nice! I suggest having it added to Gunnar's awesome annotation processing list

Lombok is not Java. Unlike, say, Immutables, Auto and other annotation processors, it is not some supported add-on, but a piece of software that significantly modifies how the javac compiler works. It is essentially and technically a fork of javac, and, therefore a different language from Java.