jte VS Micronaut

For java/Kotlin, we are using JTE (https://jte.gg/#getting-started), pretty nice build tooling and IDE support to generate pre-compiled templates without additional code generation steps.

Thanks for the hints! I created an issue for this: https://github.com/casid/jte/issues/240

JTE is a template engine for Java/Kotlin that I've started using recently. While trying to integrate tailwind I've run into issue with the (notorious) IntelliJ tailwind plugin. I've opened a ticket with JetBrains to ask that they add *.kte and *.jte file extensions to the tailwind plugin. If anyone else is keen for this change to be made, please upvote the linked ticket.

Instead of using commonly used frameworks (like Spring Framework) I preffered to use something that is small and doesn't have "magic" in it. So I've chosen Javalin as a simple web framework, added MongoDB client libraries nad jte as template engine. To show that simple and clean looking apps doesn't need any big JS libraries I've selected chota - one of micro CSS frameworks.

Because the code is generated Java code the runtime dependency is minimal and I plan on offering a zero dependency runtime version. I believe to have one of the smallest footprints of Java templating languages and is as fast as jte.

A microframework or Spring Boot + Template Engine such as jte or Thymeleaf gets you far.

I can highly recommend https://github.com/casid/jte

Micronaut has a share of the space too.

https://micronaut.io/

However, you’re right that Spring Boot has the lions share of the Java ecosystem.

I've used vert.x in a big project once. I don't ever want to do that again. Performance is pretty good, but the developer experience is beyond clunky.

My current favourite Java server framework is Micronaut.

Great performance and easy to develop for!

https://micronaut.io/

I wonder how much you'd save with Micronaut: https://micronaut.io/

> Micronaut is a software framework for the Java virtual machine platform. It is designed to avoid reflection, thus reducing memory consumption and improving start times. Features which would typically be implemented at run-time are instead pre-computed at compile time.

https://en.wikipedia.org/wiki/Micronaut_(framework)

I don't think you'd go down to 9, but something like 20-30 could be doable.

I'd like to introduce my project. It is called mlfx. It can compile FXML ahead of time. It is basically an annotation processor, which internally uses Micronaut framework's AST abstraction and compiles fxml files directly to JVM bytecode. This decreases UI load time and also helps with native-image reflection configs. It also has some compliance tests that load compiled code and check resulting object graph against one loaded by javafx-xml. It also has some drawbacks now, but, please, read README. Now I'm successfully using it in two production projects.

https://micronaut.io/ https://quarkus.io/

when it comes to full stack frameworks, Micronaut(https://micronaut.io/) is actually good and pleasant to work with.

For the server Quarkus and Micronaut might be interesting besides Spring Boot. Quarkus is more popular and backed by RedHat (so probably here to stay).

🥇 Spring Boot 🥈 Quarkus 🥉 Micronaut 🏅 Ktor 🏅 http4k

Spring boot is still The King. Although I've not done more than hello world with Micronaut, it might have easier learning curve than Spring (and concepts are similar to Spring so you can carry over later to learn Spring). It could also be a useful skill in world of microservices these days.