record-builder VS Immutables

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.

This 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/issues/1358 https://bugs.openjdk.java.net/browse/JDK-8281238

That's good, but I prefer this : https://github.com/immutables/immutables It has all sorts of neat stuff like lazy, defered, cached, defaults etc. Just needs updating to use records.

Not bad :) I like using Immutables (which is backed by the style of implementation referenced in the link in https://github.com/immutables/immutables/issues/450)

Annotation processors? Like Immutables? Those already exists, but the major difference is that an annotation processor cannot change the processed class, but has to create another one.

While you’re looking into this I would highly recommend checking out immutables. https://github.com/immutables/immutables It is pretty popular in the industry and very nice!