Reified VS Lombok

I'd like to disagree. I'm an high school student myself and I am interested mostly in programming, but also in computer science. I have never studied anything in either fields at school so maybe my opinion here is limited. The first point I'd like to address is that, while the line between computer science and programming is sometimes very thin, this project clearly falls in the latter's territory. Furthermore, being a computer scientist or a software engineer doesn't excuse an individual from not following the coding practices that regulate a particular language. While the latter is a tool in both cases, it's important in my opinion to maximize its expressivity to get the job done as efficiently as possible. At least in my opinion this is very important to understand the difference between the various programming languages, build tools and everything else as, without following the tool's philosophy at heart, they start to look all the same very fast. Finally a computer scientist could have an interest in being a good programmer and vice versa which makes it trivial to start following good practices from the start. At least this is what I've always tried to do from my first project(https://github.com/Auties/MeteorShardSourceCode) to my last ones(https://github.com/Auties00/Reified https://github.com/Auties00/WhatsappWeb4j).

Again, Lombok does not compile anything. All it does is add plain Java objects to the AST. When Javac then compiles the AST, it also compiles the instructions injected by Lombok. It is nothing hacky or fancy. You can see my library doing the exact same thing here: https://github.com/Auties00/reified/blob/main/src/main/java/it/auties/reified/simplified/SimpleMaker.java

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/