groovy VS Micronaut

This time, I visited Groovy. Given my biased first impression about Java and the JVM, I wasn't too exited! But I couldn't have been more wrong! 😁

The default programming language is Kotlin instead of Java. Also, Build configuration language is nowadays Kotlin DSL (build.gradle.kts) instead of Groovy DSL (build.gradle), the past default.

There are languages that are more like "script versions of java", lately including java itself - you can run simple .java stuff directly with a shebang line now - but things like Beanshell of yore and Groovy are far more java-like than javascript.

Install Groovy: To use Groovy, you'll need to first install it. You can find the installation instructions on the Groovy website (https://groovy-lang.org/)

On https://groovy-lang.org a lot of big companies are listed which use(d) Groovy. Is this still current? E.g. Netflix, ...

Groovylang

Hence, Groovy

If you want the power of JAVA but the feel of PYTHON, try Groovy (https://groovy-lang.org/) . Basically a scripting lang for JVM but can be dynamically/statically compiled and is 100% compatible with all JAVA libs but looks like Python

Doesn't Groovy (https://groovy-lang.org) achieve much of this? I remember being taught with it at university for some time before they introduced Java. With Groovy you don't need the class or main method, and can have a program which is just `println "Hello world!"`.

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.