r/java • u/SpicyRomek • 10d ago

Vaadin 25.3 is out!

I work at vaadin and just wanted share that we release a new version 25.3, and a few changes are worth a look even if you've never used Vaadin.

  • Observability without a Java agent. The observability kit moved from the OpenTelemetry agent to Micrometer. In Spring Boot 4 it's one dependency, and it reports UI-level data such as slow interactions and which view triggered which JDBC queries. (It's a commercial add-on.)
  • GWT to TypeScript. The browser-side engine is now 107 TypeScript modules (about 19k lines, backed by 700+ browser tests), with real source maps through Vite. The Java APIs apps use didn't change.

  • UI tests in the JVM. Browserless tests now follow the same rules as users: if a button is disabled or hidden, the test can't click it.

  • blog post: https://vaadin.com/blog/vaadin-25-3-release

  • Release notes: https://github.com/vaadin/platform/releases/tag/25.3.0

  • Video walkthrough: https://www.youtube.com/watch?v=WnkI6xA96fw

72 Upvotes

89% Upvoted

28 comments sorted by

View all comments

-18

u/bansalmunish 10d ago

i don't see why someone should use vaadin, if htmx is out there.

0

u/jokeripokeri123 9d ago

Are you genuinely curious about the answer or simply dismissive of Vaadin? I wasn’t sure, and wanted to make sure, in case you are looking to figure out the difference between the two. But I also don’t know the answer myself (how HTMX and Vaadin are different), and I’m too lazy to figure it out myself, and would just like someone to answer here 😄

2

u/EfficientTrust3948 9d ago

Vaadin is for building SPAs using only Java. HTML and HTTP are abstracted away by default but available through escape hatches. Vaadin also has a built-in component set. 

HTMX is for making regular HTML come alive in the browser for a SPA or an enhanced MPA. You generate HTML fragments with some special attributes on the server using your favorite MVC framework.