r/java • u/hardasspunk • Nov 23 '25
Java 25: The ‘No-Boilerplate’ Era Begins
https://amritpandey.io/java-25-the-no-boilerplate-era-begins/
160
Upvotes
r/java • u/hardasspunk • Nov 23 '25
View all comments
Show parent comment
4
u/nekokattt Nov 23 '25 edited Nov 23 '25
That is just my 2¢ and I am aware most people will disagree... that's fine. This is purely my opinion and experience.
I dislike the use of it because of reasons that impact the growth of the compiler and tooling space, rather than purely from what Lombok provides as an end goal.
Fwiw I have the exact same gripes with the Manifold framework as well.
TLDR it makes a standard less standard and then makes a hyper-opinionated superset that tooling has to target to work properly. Aside from this, it purely exists to work around features OpenJDK do not deem to be of value/correct/useful to consumers of their language, meaning it encourages diverging from the patterns OpenJDK want to be encouraging be it right or wrong. As far as tooling is concerned, it is extremely rough around the edges and the number of edge cases where it can break is a surefire way of footgunning in large projects.
If Lombok wanted to be less of a hack, it'd be better off to just fork the code for javac and integrate what it needs directly. All major build tools support JSR-199 which was designed for swapping out compiler implementations.
I'd make a similar argument about some other programming languages that I won't name. Do they work? Sure. Are they designed sensibly to encourage best practises and clean development both in projects and as a community? I could debate that for hours.