Nice, liked Lombok! But why stop there, Scala / Kotlin have everything you have in Lombok + Java 8 (case class in Scala and data class in Kotlin do basically what @Data does, in Scala there are no checked exceptions by default, and both have very good null safety solutions, albeit different approach)

I think that if a company is open to using Java 8 + Lombok, then they should at least try out Scala / Kotlin (or even xTend) for comparison.

If compile times are what worries you, Kotlin seems to be on par with Java compilation times, although I don't think Kotlin is production ready yet. (and it misses some Java 8 / Scala goodies such as parallel collections etc... though I'm sure JetBrains will add it soon...)

Did you have a look at Xtend's Active Annotations? http://www.eclipse.org/community/eclipse_newsletter/2013/mar... You can define your own annotation processors without having to understand Java Byte Code. With Xtend, an annotation processor is basically a small Java code generator that can add/remove/modify classes/interfaces/fields/methods. It's quite awesome for automating design patterns, e.g. generating getters/setters, observer pattern, property objects, delegators, etc.

Anyone with any sense of taste avoids Lombok. It's a terrible hack. Rather use Scala which gives you far more. Maintaining Lombok + Java is a pain.

I dislike nearly everything about Lombok but `val`. Everyone else seems to be the opposite :-(