avaje-inject VS Lombok

Avaje Inject has quickly become one of my favorite libraries. Inject is basically like Dagger if Dagger was focused on server side instead of Android. It's a tiny lib (~76kb) that uses the power of annotation processing to generate DI classes. Recently I've been using it for AWS lambdas and it works pretty great.

https://avaje.io/inject/ - Implements JSR-330 and JSR-250

Have you tried out Avaje inject? It's currently my favorite DI lib.

Been building a web service with avaje inject and avaje http lately. It has a very spring-like feel for a DI lib, (Lifecycles, Test annotations) but the libs are tiny and totally reflection free through codegen.

Avaje is pretty cool, it's a compact DI library based on APT. https://github.com/avaje/avaje-inject

Like avaje inject ? DI as source code generation done at build time?

Just to say, I also created a DI library called avaje-inject - https://avaje.io/inject/ ... which uses Java annotation processing to do DI as mostly source code generation. So the runtime dependency is ~ 67Kb. It also supports AOP aspects via source code gen which I think is kind of cool - you can have your own aspects like `@Retry` etc and it's actually done using source code generation.

I am a bit fan of using annotation processing (source code generation) to simplify things - DI https://avaje.io/inject/ , JSON binding (https://github.com/avaje/avaje-jsonb) and rest servers and clients (https://avaje.io/http).

Dagger2 and avaje-inject are other options (DI as source code generation via annotation processing). https://avaje.io/inject/

The above class maps the json data to a java object we can work with. We use Lombok to generate constructors, getters and setters for our code and the Jackson Project to handle serialization and deserialization of json to pojo . We know the response is an array of objects representing the coffee and so above data structure is fit for this.

Almost a decade ago, I started reducing my boilerplate (and saving time with Lombok. It made my life much easier, simple as that. Ever since I've been looking into finding the smoothest solutions for saving time rather than handling all of it myself.

Lombok is a widely used library that simplifies Java code. The @NonNull annotation helps enforce non-null parameters, generating appropriate null checks:

Project Lombok

I gotta agree with /u/rzwitserloot I don't see anything in the lombok repo that indicates they have their "own compiler". I see the "reaching into javac internals" but that's it.

i looked into that and found this: https://github.com/projectlombok/lombok/issues/2310

Funny enough; /u/rzwitserloot is the author of Lombok, one of the most widely used Java libraries in the world. So it's not really some kind of random-ass Redditor they're having a discussion with either.

This removes the need to add the 'Project Lombok' library (and going through a phase of installing it in your Eclipse IDE; old school devs know what I am talking about) and speeds up development time. Java 14 added a new feature of 'Records' which allows you to do the same, but it doesn't offer a 'copy' method to ease your object creation and also enforces the 'final' keyword for variables making them immutable.

I get the main criticisms of Java, i.e. its verbosity and the requirement for a lot of boilerplate code, and understand why some people switched to Kotlin. But by using libraries such as lombok you can get rid of most of it and suddenly the incentives for switching aren't that big anymore. And in the end it's all JVM bytecode anyways.

I usually use this... https://projectlombok.org/