jstachio VS Lombok

Anyway it was one of the reasons we (my company) went with Mustache and why I wrote JStachio.

I don't know Dart that well (only experimented with simple apps) and just kind of lurk on this sub but I am the author of a HTML templating language (Mustache) in Java that uses annotations and code generation: https://github.com/jstachio/jstachio

Things like this https://github.com/jstachio/jstachio (author) would not be possibly with just an include like preprocessor.

Hey guys, wanted to share my project JStachio with you all. It's a java templating engine that's like Mustache.java and Handlebars.java in syntax but also compile time type safe like JTE, Rocker, and Qute.

On a related note I have been really liking the newer Java feature of being able to execute .java files directly. I have been using them frequently to execute what would normally be a Bash or Python script. I actually have a Java .java script that mimics some parts of the Maven release plugin and because Java speaks XML really well it was easier to implement it in Java than Bash or some other scripting language which makes me think /u/bowbahdoe point on including a JSON parser with the standard lib would be very useful.

I plan on releasing an unpoly (htmx like library) petclinic using my templating library https://github.com/jstachio/jstachio (superior to thymeleaf but I’m biased) and some avaje + Jooby. Hopefully next month.

But going back to they can generate whatever they want they could even make an expression or template language that is type safe (and I know this is possible as an author of such a library).

For those that do not like the syntax and still want compile time string interpolation check out my library: https://github.com/jstachio/jstachio

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/