We were pretty excited about SPA frameworks when they first came out. Now that I look back, I have to admit that none of our SPA-based apps (Vue, Angular and React) should have been done in an SPA. Building complex logic on the backend and then building all of that state management stuff on the front end .... and then having to maintain all of that complexity over the years has not been fun. And what did we gain? Nothing really. Don't get me started on keeping npm packages current. If you are in that 1% of applications (and that is generous) that needs the front-end horsepower and has a massive number of users, go for an SPA. If not take a serious look at HTMX, Unpoly or Hotwire.
really great tool, created many new application with thymeleaf after i have done a few enterprise apps with angular and react. Easier to learn, take less time to create apps. I split thymeleaf apps from the backend who use rest.
Love Spring and have done for years and will continue to do so. But I will never write a front end in Thymeleaf ever again when exists React or VueJS. Spring is almost second to none when writing API's nowadays, but front ends, I'll pass.
Didnt you guy not hear at all what this guy exposed with HTMX?, with HTMX you can make the transition, REACT, VUEJs is slow, if you want somehting now use Qwick instead, but here, you have a very incredible simple way to express Thymeleaf reactive!
making technology decisions isn't always whats faster. thymeleaf has nowhere near the support or adoption for it to become an alternative. @@gonzalooviedo5435
Didnt you guy not hear at all what this guy exposed with HTMX?, with HTMX you can make the transition, REACT, VUEJs is slow, if you want somehting now use Qwick instead, but here, you have a very incredible simple way to express Thymeleaf reactive!
We were pretty excited about SPA frameworks when they first came out. Now that I look back, I have to admit that none of our SPA-based apps (Vue, Angular and React) should have been done in an SPA. Building complex logic on the backend and then building all of that state management stuff on the front end .... and then having to maintain all of that complexity over the years has not been fun. And what did we gain? Nothing really. Don't get me started on keeping npm packages current. If you are in that 1% of applications (and that is generous) that needs the front-end horsepower and has a massive number of users, go for an SPA. If not take a serious look at HTMX, Unpoly or Hotwire.
really great tool, created many new application with thymeleaf after i have done a few enterprise apps with angular and react. Easier to learn, take less time to create apps. I split thymeleaf apps from the backend who use rest.
Thank you for sharing, it's been very informative!
Merci beaucoup pour votre travail et partage
I can't believe this video is from 2022. HTMX explosion is just 2 months ago, and you guys think about it a year ago!, damn, The world is very fast!.
The talk was very useful 🎉❤
Love Spring and have done for years and will continue to do so. But I will never write a front end in Thymeleaf ever again when exists React or VueJS. Spring is almost second to none when writing API's nowadays, but front ends, I'll pass.
Didnt you guy not hear at all what this guy exposed with HTMX?, with HTMX you can make the transition, REACT, VUEJs is slow, if you want somehting now use Qwick instead, but here, you have a very incredible simple way to express Thymeleaf reactive!
making technology decisions isn't always whats faster. thymeleaf has nowhere near the support or adoption for it to become an alternative. @@gonzalooviedo5435
Thymeleaf is bad, I prefer using angular or other typical frontend frameworks
Didnt you guy not hear at all what this guy exposed with HTMX?, with HTMX you can make the transition, REACT, VUEJs is slow, if you want somehting now use Qwick instead, but here, you have a very incredible simple way to express Thymeleaf reactive!