Why we built Hilla: the modern web framework for Java

Does the world really need yet another frontend framework? We believe it does.

With Hilla, you can build enterprise-grade web apps faster by seamlessly combining server-side Java and client-side TypeScript, instead of developing the frontend and backend separately.

In this live stream, Product Manager Leif shares his vision behind Hilla and shows code examples.


Host: Marcus Hellberg
Presenter: Leif Åstrand

[arnaudpoutieu]

Great job, all my congrats to the entire team!!!!

Thank you @Leif Åstrand to mention the Server sent event support, and I'm personally kin to see how it works

[eloundoumvogo]

Hilla is amazing thanks for that amazing tools guys !!

[TomerBenDavid]

Do you have an example of taking some random react component and incorporating it in a hilla project? This would be great!

[bhuvaneshvarsrivastava]

I find this awesome framework, guys.
Is there any devtools also to see the state data and everything in browser itself ?

[artemv]

on 10:45 you talking about moving connection point of frontend dev and backend dev to services APIs. Can't understand really benefits of it. Now you need to coordinate services APIs instead endpoints.

UPD: Okay, I got it, it is better because you as frontend developer can control the payload, that sended by the network, and data returned by services is not really creating any overhead so you can use it more freely.

[protectedmethod]

The link in the description is broken due to the exclamation point

[lars]

Using the generated names in the frontend isn't a good idea. You see that when you change any name.

A solution for that is to use a mapper. So you have the change only on one position.

[kuhaniresti]

So the endpoint is readily available to typescript after saving java class file?

[anonymousyoutube]

How does this compare with Grails? There used to be a Vaadin plugin, but it is very out of date.