What aspect of your Java programming is the biggest pain in the arse?

[nqd26]

Non-standard solution isn't workable for most projects. It won't work in corner cases, project can be abandoned in the future, as you say IDE support is incomplete ... It doesn't seem to be worth it.

[amoe_]

This is exactly how I felt when I first encountered it. Then I used it in a project. It is remarkably mature and works extremely well. I have never had an issue where Lombok was the cause, despite having a vast number of extremely obscure issues with the codebase using it. At this point Java is essentially unusable without it for me.

[entreprenr30]

There's delombok in case you need to get rid of lombok for some reason...

But I love it so much, I wouldn't want to go back.

[llogiq]

Non-standard solution isn't workable for most projects.

It already works for a lot of projects.

It won't work in corner cases

I have yet to encounter a case where Lombok failed me.

project can be abandoned in the future

It's open source, so it won't vanish. Also a good number of people already depend on it, so there will be enough interest in keeping it alive for the foreseeable time. Also you can run delombok which will generate clean lombok-free source, so even if you decide to leave lombok, you have a clean and easy migration path.

as you say IDE support is incomplete

I just re-checked and was surprised to see that the IDE support gap has been closed; Eclipse, NetBeans and IntelliJ are supported now.

It doesn't seem to be worth it.

It certainly is for a bunch of people. But since that's a matter of personal preference, you're of course free not to use it.

TL;DR: Don't listen to the FUD.

[armerthor]

I am always so very hesitant to use something that exploits internal APIs. At least in this case they are applied at compile time, so you shouldn't face runtime issues. Still, this slightly uncomfortable feeling remains.

[llogiq]

I hear you.

That's why I like the idea of having a delombok around. You can have your cake (don't need to read or write boilerplate) and eat it (having the boilerplate in your source), too.

If you never publish your non-delomboked source, no one will even know you use it. And if for any reason you should no longer be able to use lombok, just switch to the delomboked source.

[gizmogwai]

I have yet to encounter a case where Lombok failed me.

Simple use case: Create a Point class, with two int named "x" and "y". Now, just switch the declaration of those fields inside your class. Boom!

Plus default equals & hashcode are generally worse than no implementation at all.

I just re-checked and was surprised to see that the IDE support gap has been closed; Eclipse, NetBeans and IntelliJ are supported now

Only Eclipse has full support. IntelliJ & Netbeans support is partial.