In this video, Marcus shows you hands-on how to build a modern web app, fully in Java. The Vaadin Flow framework lets you define your views in Java while running them as modern web components in the browser. With full Spring support, this may be the fastest way to build a frontend for a Java backend.

PUBLICATION PERMISSIONS:
Original video was published with the Creative Commons Attribution license (reuse allowed). Link: https://www.youtube.com/watch?v=b9QI9JRSLi4

****
INTERESTED IN THE STOCK MARKET?
I developed a profitable trading model that generates high probability BUY & SELL signals on S&P500. To learn about it, visit https://yuriymatso.com/sp500-model/

source

20 Comments

  1. Excellent video to show how useless Vaadin is. Vaadin tries to imitate, although very badly, what is available in Android and in Java Core for desktop, except for the most important stuff such as Shapes, vector paths, etc. Vaadin makes very clear that it is not how UI and WYSIWYG problem are going to be solved in the web. We do have a crisis in UI and typography in the web that can only be solved with inclusion of vector graphics, not with its exclusion. Vaadin is just the framework aspect for creating useless layouts with totally obscure coding, calling it "Java" (How dare you? would say Greta). In my opinion, the framework aspect is exactly what should be thrown away. This not only discredits Java as a programming language for the web by just ignoring its powerful awt JRE library, but also discredits Java's potential to do coherent applications on the web.

  2. That was a really well made video about an interesting technology. I don't understand all the negative comments here. Of course this is not the best practice for all kinds of web applications and has some drawbacks to consider, but I could think of some cases where this would be a really good solution.

  3. Wonder why someone gonna want to use static type language on dynamic language runtime? There are of common workflows in JavaScript that should not work in this Java app.

  4. Is anybody in 2022 still writing this type of monolithic applications with tightly coupled frontend and backend logic? The communication between client and backendserver can not be reused for coupling with other systems, frontends or automation. Also many backend developers tend to not being good at layouting a frontend and frontend developers usually don't want to get in contact with repositories and the whole backend stuff. Keep both worlds separated and use a commonly implementable interface like REST. And you can write easily good and maintainable backend services with Spring, Quarkus or JEE. No need for Vaadin, imho.

Leave A Reply

Please enter your comment!
Please enter your name here