(After all, GWT ran on top of that exact tech) Frontend capabilities of browsers were pretty good, if you knew what you were doing. > GWT had a place back when the frontend capabilities of browsers were very very badly balkanized and pathetic.Įverything that GWT did, frontend-wise, could be done just fine in any of the 'pathetic' browsers back then. For paying clients, they typically request REACT. For personal projects I will always use Vaadin. I think REACT and Vaadin are similar for me (in the sense that I can get a lot of high quality work done quickly). Though you need to be good at multi-threaded coding.įYI, I don't work for Vaadin. No need to mention how awesome PUSH technology is. I use it extensively to have my web pages op up quickly, then slowly get filled out as the APIs return. Vaadin also supports PUSH technology out of the box. Using Selenium is huge cause I can get answers to my questions about testing by searching for the Selenium answer that I can apply in my tests. So I quickly create a breaking test using the Vaadin testing framework. It makes it really easy for me to do TDD on my frontend code. Vaadin has a really cool testing library. For multiple site apps, I had to create my own solution that relied heavily on Servlet Filters to dynamically return the PWA files. Vaadin has support for PWA for single site apps. After using it for a while, I find myself wanting to use my own components, versus the many components Vaadin provides out of the box. So far I have not ran into a problem I could not fix yet. You can really leverage the years of experience in Java backend on your frontend. #Vaadin ui browser code#What I really love about it is that I am able to code my frontend apps just like my backend microservices apps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |