Georgios Andrianakis

@geoand86.bsky.social

Principal Software @ Red Hat, working on Quarkus, Langchain4j and others

Sooo, we've just released the @quarkus.io MCP server 1.0.0 🎉. The main branch is now 1.1 and we already have a couple of new features for this milestone: client sampling, Dev UI improvements and CLI adapter github.com/quarkiverse/.... We also started to look into the new spec version. Stay tuned!

1.1.0 Milestone · quarkiverse/quarkus-mcp-server

This extension enables developers to implement the MCP server features easily. - 1.1.0 Milestone · quarkiverse/quarkus-mcp-server

github.com

Remember, there is an intrinsic feedback availability imbalance: we deal with bad stuff daily, and it is more visible than good stuff. For every ugly customer support ticket, there are likely hundreds of customers who never told you things were great.

Believe it or not, the next release of Quarkus will be the 365th release since Quarkus became a thing, 6 years ago. It will be one year of release days! I released the large majority of them but this will change a bit with @janmartiska.bsky.social taking the responsibility for some LTS streams!

I love just how free the new AOT cache is! For the a sample Quarkus application, normal startup time was around 400ms on my machine (JDK 24 EA). When using the new AOT cache feature with JDK 24, the application starts in around 270ms. And all that without a training run! bsky.app/profile/dani...

Daniel Oh@danieloh30.bsky.social · 2y ago

Quarkus 3.19 - UBI 9 images, Micrometer to OpenTelemetry bridge, JEP 483 new AOT cache... quarkus.io/blog/quarkus... @quarkus.io

For Quarkus, we often ask for simple reproducers when users report an issue. It might seem like wasted time for you but it's not. It happens often that the information is not enough to reproduce the issue and trying to guess how we can trigger the error is a massive waste of time on our time. 🧵