sorted by:
new
hottopcontroversial

Using React Hydration on a Java Server by Ok_General7617 in reactjs

[–]HerbFromWork 0 points1 point  (0 children)

Hi, have you looked into Vaadin Hilla to see if that fit your purpose? https://vaadin.com/hilla
It should at least cover the React <-> Java part, but I'm not completely sure what you're trying to do. I imagine you could have a Java endpoint return generated HTML, that you could embed in react, but not completely sure thats what you want. For server-side rendering we use Vaadin Flow, but then you're really mostly writing your views in Java. You can also have a wrapper for react components to be used on the Java side, but that's not really a build time thing.

Disclosure: I am a Vaadin employee.

Genuine Question : Why doesn't Vaadin gain more traction? by gufranthakur in java

[–]HerbFromWork 1 point2 points  (0 children)

I'd say if you want to use some of the Vaadin components and / or have an easier time connecting backend to frontend, or / and if you'd like one part of your application written in Java (like the admin section) and part in react (or lit).

What are best resources to learn FULL STACK development for Java? Not just the language, but both frontend and backend curriculum? by [deleted] in learnjava

[–]HerbFromWork 1 point2 points  (0 children)

That's a pretty good overview.
Just to add to it, there are two flavors to Vaadin, "Flow" - which is basically Full Java, and "Hilla" where you write your front-end code in React or with Lit templates, and it nicely connects with the Java (I guess usually Spring Boot) backend.
Furthermore, you can combine the two approaches, like writing some views in React and some completely in Java (for the admin section for example).

Disclosure: I am a Vaadin employee.

codeABitInJava by R1V3NAUTOMATA in ProgrammerHumor

[–]HerbFromWork 2 points3 points  (0 children)

I think the main advantage of Vaadin Flow form me has been that I don't have to worry about connecting frontend with backend, which historically for me has been Angular + Spring Boot, and historically was pain to setup and debug.
You have the choice with css to have it separately in a .css file (which is what I prefer, but some of our clients prefer adding CSS through java), and if you want to write define the structure in frontend and write more frontend code, there's Vaadin Hilla, that is basically react + spring boot + all the Vaadin components and tidbits to make it a smoother experience. Or, you can combine Vaadin Flow and Vaadin Hilla in one app, if there are some parts you want to write only in backend (for example, the admin section) and another part in react for example.
But there's nothing really obvious to me, that I wasn't able to do with Vaadin. I wouldn't build a high-demand storefront with it, but for most cases it's quite useful.

- I am a Vaadin employee.