Quarkus Insights

Martin Kouba joins us to discuss the basics of Qute, the templating engine which allows to build web applications using server-side templates.
Demo app: github.com/mkouba/qute-insights

[@Douglas-Allen]

Very nice! I’ll be checking out Qute in extreme detail. And we’re still rocking with server side Java web apps in 2024🔥

[@user-xw7xp2xv8e]

I love this video!❤

[@vollpfosten8726]

Thanks for the presentation, Martin! I am using Eclipse, too. Which plugin(s) do you recommend for working with Quarkus and Qute templates?

[@zone66]

using qute for email-templates and templates for PDF generation in the backend. So far im pretty satisfied,
but qute focusses a bit too much on the web part for my use-case, and i need to pave a way for my use-case a bit more.
for example:
- including assets like css-files from the classpath or filesystem directly into the template would be cool.
- i would like to have as much qute functionality without making my backend a web-server that shares assets to the outside (security)
- typesafety is cool, but writing a typesafe method for all internationalization messages is a bit bothersome, but its ok.

[@razt3757]

Why would I use a #fragment when I can just use hx-boost instead?
Using boost you don't need to reload the whole scripts contained in the updated frame, so the only extra cost is the chunks contained in your body element.
So letting aside the few bytes you don't waste, what's the advantage of adding such complexity?
And how would you debug fragments?

[@user-ss4hx4ut2x]

You can’t use hx-boost on all elements. And as a matter of fact, htmx introduced the concept of fragments and other frameworks adopted this idea.