Micronaut Framework 4.10.5
The Micronaut Foundation is excited to announce the release of Micronaut Framework 4.10.5 ! Please see our latest blog post for more details. micronaut.io/2025/12/17/m... #micronaut
I am mind blown. I asked Claude to port Ratatui to Java, using Gradle, create a demo app and compile it to a native binary. It took 20 minutes. Here's the demo (this is a native binary compiled using GraalVM using the official native build tools plugin). 🫳🎤
/cc @glaforge.dev @maxandersen.xam.dk
From JIT to Native: Path to Efficient Java Containers: medium.com/graalvm/from... by @olyagupalo.bsky.social
#Java #GraalVM #Micronaut
Not sure there has ever been a technology that made me want to ragequit software development completely like Lombok does. Somebody kill it with fire please.
Source code generation from JSON schema with @micronautfw.bsky.social micronaut-projects.github.io/micronaut-js...
Generate Maven and Gradle plugins from common code using @micronautfw.bsky.social sourcegen micronaut-projects.github.io/micronaut-bu...
Nice! @micronautfw.bsky.social 4.8 now ships with HTTP client and server implementations that use the built-in JDK client and server. You can build GraalVM compatible Micronaut applications with no third party dependencies micronaut-projects.github.io/micronaut-se...
#java #micronaut #graalvm
Micronaut Framework 4.8.0
The Micronaut Foundation is excited to announce the release of Micronaut Framework 4.8.0 ! Please see our latest blog post for more details. micronaut.io/2025/04/01/m... #micronaut
Awesome "GraalVM for JDK 24 Release Stream" by Alina Yurenko and Fabio Niephaus today with the latest "GraalVM for JDK 24" features medium.com/graalvm/welc... and medium.com/graalvm/what... @alina-yurenko.bsky.social @fniephaus.com
You asked, we delivered: we merged FFM support in @graalvm.org Native Image on MacOS/AArch64!🚀😍
github.com/oracle/graal...
This means that you can now also build and run locally apps like github.com/mukel/llama3... (cc @stephanjanssen.be :))
Coming soon in GraalVM for JDK 25 EA builds!🎉
Today we are releasing Graal Languages v24.2! 🎉.
This release brings a Gradle plugin for GraalPy, scaling native Python across Java threads, Continuation API in Espresso, Truffle Bytecode DSL, and more!
What's new: medium.com/graalvm/what...
The release notes: www.graalvm.org/release-note...
GraalVM for JDK 24 is here!🎉
Higher peak performance with ML, smaller executables, enhanced SBOM support, and many more new features!
What's new: medium.com/graalvm/welc...
The release notes: www.graalvm.org/release-note...
Download now!🚀
graalvm.org/downloads/
#GraalVM #Java24
Java 24 / JDK 24: General Availability: mail.openjdk.org/pipermail/jd...
Features: openjdk.org/projects/jdk...
#java24 #jdk24 #openjdk #java
#JavaOne is 5 days away! Don’t miss out on attending the conference that started it all! Network with #Java experts from #Oracle and the community. Register now: javaone.com
This is me debugging a Rust library compiled to Wasm and embedded in a @micronautfw.bsky.social microservice in @intellijidea.com: Compile with debug info, enable the Chrome Inspector for #GraalJS and #GraalWasm, and attach to the process. 🤓
Will share more details at #WasmIO later this month!
How did we get to this point? 🤦
That is correct 👍
Right, not saying the module system doesn't add value, but it doesn't take away the need for strong build tooling.
Also application developers don't think like library developers so when an application developer is tasked to build a library they are not thinking about restricting the public API
Module system doesn’t really help uncontrolled growth of the dependency graph. It only helps isolation. Compilation time isolation can already be achieved with compile vs runtime scopes
A library that depends on X shouldn't mean that X is now usable by everyone. It is just an unbelievable crazy default.
Developers are also sloppy putting things like JUnit and Mockito without a scope and publishing a library. Now those are public API and the transitives of those public as well.
This becomes worse in larger organisations as internal libraries are produced that export more dependencies and then these transitives are consumed by everyone until the point that "the platform" everyone builds on includes hundreds of APIs. Removing a transitive results in breaking changes.
Part of it is our fault I guess. We create higher level abstractions that encapsulate functionality (frameworks) that provide tremendous value and allow devs to do less and less because batteries included. These frameworks are very modular and allow configuring only what is needed, but no one does.
We work at the same company, come help me fix our issues with it 😉
Don’t think there as any easy answer to that. Gradle can be just as bad though does give you more control of resolution rules.
In large organizations it is difficult to control transitives and because with Maven transitives become public API automatically effectively every dep is public API
#Micronaut Framework 4.7.0 is out!
Learn about the latest enhancements, including support for LangChain4J to integrate LLMs into Java apps, and improved support for Graal-based dynamic languages.
Read more on #InfoQ 👉 bit.ly/41c0rxa
#Java #LLMs #SoftwareDevelopment
Oh and AI is only going to make it worse.
Unpopular opinion: Maven used at scale causes untold damage and keeps thousands of Senior Architects busy and employed policing uncontrolled dependency graphs from end-less copying and pasting of <dependency> snippets found on StackOverflow
Micronaut Framework 4.7.0 Provides Integration with LangChain4j and Graal Languages: www.infoq.com/news/2025/02...
New release: Graal Development Kit for Micronaut 4.7.3!🎉
It contains Micronaut® framework 4.7.3, software supply chain security enhancements, new hands-on labs, and more.
See what's in this release: blogs.oracle.com/java/post/an...
