I even have this experience on my own projects and with much shorter span than a year.

> Annotation-based programming might seem cool now, but wait a few years.

I really don't know anything 'better'(time wise) to accomplish the same thing though. So when you start it's very easy to just add some Jackson annotations and you think it's going to be smooth sailing from now on add some complexity down the road and you just use some stackoverflow recipes to do the thing I want (without any in-depth Jackson knowledge) and it still is ok-ish add some more complexity down the road and then you feel the frustration of using Jackson.Īdd in some web annotations, security annotations, ORM annotations, logging, test annotations and so on and it's the same story - you are in fact doing something very complex and when you depart from the happy path of using the functionality via annotations, it gets quite frustrating. Sure, it's very easy to add Jackson, but people severly underestimate the problem of JSON POJO mapping(multiple ways of doing it and different programmers wanting to do it in different ways). Java is not the most powerful language, yet it has huge adoption the main reason is the number of quite OK and very powerful libraries. I don't have absolutely anything against small projects, I'd love to work more on smaller projects, but 18000 lines of generated code is NOTHING, try to convince a medium team to use Lombok, you'll very soon end up with people loving or hating it, removing it for debugging purposes, creating their own generators and very soon it's a real mess.īut all that is just my experience, I'm not trying to dismiss Lombok or any approach, if it works for you, great! There are other highly opinionated frameworks/stacks that have mixed adoption in the java world - jhipster seemed to gain some traction, but people seem to just use bare spring boot nowadays(which is quite opinionated) some 10 years ago, but the idea seemed to have died down, maybe it's my own bubble.Īutomagic is ok for a specific type of problem (Rails for webaps?), Lombok however reminds me a bit of the promises of AOP which failed to gain traction outside frameworks. Sure, I've seen Spring/J2EE projects that used Lombok. Yes, but as a programmer when I'd start working on a new project, I would call it a Rails project, I've never heard of a Lombok project.

Visual studio code java maven lombok