Thank you Mati for this insightful record. I have to admit that HTMX is a serious tool on which we backend guys should really consider diving into to fill the UI gap we sometimes face
Thanks Mati for your video, it helped me a lot in my project. I did not have to spend hours to learn Javascript and React to make a simple UI, cheers :)
Thank you very much Mati for sharing this demonstration of how HTMX with Thymeleaf can be used with Spring Boot. I plan to start testing this further myself. I'm curious to see how effectively different elements of the web page can be "componentized" and reused, such as to compare with the ease of JSX components in React. For instance, in your example, after you copied the statuses list generation html from the feed.html into the statuses.html, I hoped to see if the duplication could be removed by having the feed.html now somehow use the fragment from the statuses.html. Again, I'll now explore further. Thanks for providing a starting point!
Thanks for the great comment! The reason I duplicated the code is because I didn’t do the extra work of creating a Thymeleaf component, but that is indeed possible.
Hello Mati, thanks for the video! Queria consultarte si htmx ganara terreno en cuanto a los otros frameworks angular , react? Y tambien en cuanto a IA si publicaras algunos videos.
Hola! HTMX está ganando terreno entre los desarrolladores de backend (Java, Python, Go). Es una buena alternativa para evitar usar JavaScript en el frontend. Pero no va a alcanzar a tener la popularidad de React o Angular. Le falta mucho para poder “reemplazarlos”.
Not to mention that server side html serving is more secure. That way the backend is authoritative as every request goes under authorization check and will be served only with the bare minimum viewable data.
Ok, this is very concerning for me as someone who has been doing Java/Spring back-end for 20 years, and creatng RESTful API's in the traditional way with JSON. I like the Tutorial, but this is an OLD MONOLITH. I know 'monolith' is now an over-loaded term because of Microservices. But, in the sense 'OLD MONOLITH' means you have created an application with both front-end AND back-end in ONE JAR file. We got away from this years ago, and had 'separation of concerns' which this NOW violates. I'm more interested in seeing a already done RESTful API on the back-end, one that has API's for JSON an one that has API's for HTML. Then create a SEPARATE front-end, that can call the RESTful UI API's that return the HTML snippets. This would probably ne a nice real-world tutorial. Thanks for the tutorial, it is helpful, but doesn't quite fit what I am looking for.
Hi! I appreciate your thoughts. The intention of this is not to create a monolithic app. This tutorial shows how you can create a front-end application without using JavaScript. How you structure your architecture is up to you. You can have it as monolith, or you can have multiple microservices that serve JSON, and some services will be in charge of serving the UI. The point of this tutorial is to show that a front-end can be written with HTML without using JavaScript. In the tutorial I’m hardcoding the list of posts that are being printed, but those can come from, and most likely will in a real scenario, a REST API in a different service or even a third party company. I hope this comment clarifies it. Thanks for your comment!
![TEEDEE TADA - DIAMOND NARAKORN X LEGO LYKN [Special Dance Performance]](http://i.ytimg.com/vi/QgtZedFeumA/mqdefault.jpg)
![[LIVE] : ONE ลุมพินี 83 วันนี้!! คู่เอก "พันฤทธิ์ vs ซุปเปอร์บอล วันของโอม MBK"](http://i.ytimg.com/vi/1b4pkKHa_Fk/mqdefault.jpg)
This is the best htmx, thymeleaf tutorial I have seen. Please keep creating more!😅
Thanks for the feedback! I'm glad it was helpful!
Didnt understand the HATEOS principle of returning a reference until this video. Thanks for that!
Thank you Mati for this insightful record. I have to admit that HTMX is a serious tool on which we backend guys should really consider diving into to fill the UI gap we sometimes face
I’m glad this was helpful!
Definitely, we need to pay close attention to it and its development!
Thanks for the comment!
Thanks Mati for your video, it helped me a lot in my project. I did not have to spend hours to learn Javascript and React to make a simple UI, cheers :)
I’m so glad this was helpful! You are welcome!
Geep going mate, great tutorial. Hope to see more on those topics soon. Cheers!
Thank you very much Mati for sharing this demonstration of how HTMX with Thymeleaf can be used with Spring Boot. I plan to start testing this further myself. I'm curious to see how effectively different elements of the web page can be "componentized" and reused, such as to compare with the ease of JSX components in React. For instance, in your example, after you copied the statuses list generation html from the feed.html into the statuses.html, I hoped to see if the duplication could be removed by having the feed.html now somehow use the fragment from the statuses.html. Again, I'll now explore further. Thanks for providing a starting point!
Thanks for the great comment!
The reason I duplicated the code is because I didn’t do the extra work of creating a Thymeleaf component, but that is indeed possible.
Very easy, excellent content. Thank you Mati.
Sir, can you create a playlist for springboot thymeleaf htmx so that we can learn how this technology works together.
Hello Mati, thanks for the video! Queria consultarte si htmx ganara terreno en cuanto a los otros frameworks angular , react? Y tambien en cuanto a IA si publicaras algunos videos.
Hola! HTMX está ganando terreno entre los desarrolladores de backend (Java, Python, Go).
Es una buena alternativa para evitar usar JavaScript en el frontend. Pero no va a alcanzar a tener la popularidad de React o Angular. Le falta mucho para poder “reemplazarlos”.
@@programmingwithmatigracias por responder Mati. Espero en los próximos años se vea una evolución..
I'm also backend dev who hate js, I'll try it tomorrwow jahahha
what happened to spınner gif? Why didnt it work?
nice, but should use a Thymeleaf fragment instead of copying all that HTML :)
Thanks for the advice! I’m not an expert in Thymeleaf, but I’ll be learning more about it soon!
htmx and picocss
can you guide me to make a complete springboot project with html css JavaScript?❤
I’m preparing more spring boot tutorials for the future.
@@programmingwithmati I will subscribe you to learn more about springboot:))
Not to mention that server side html serving is more secure. That way the backend is authoritative as every request goes under authorization check and will be served only with the bare minimum viewable data.
Thanks man very good tutorial
This is an easy way to hack the frontend world, react developers beware, we are coming 😂
great❤❤❤❤
I'm front end who hates and loves JS, depending on how much hair is left on my head.
Ok, this is very concerning for me as someone who has been doing Java/Spring back-end for 20 years, and creatng RESTful API's in the traditional way with JSON. I like the Tutorial, but this is an OLD MONOLITH. I know 'monolith' is now an over-loaded term because of Microservices. But, in the sense 'OLD MONOLITH' means you have created an application with both front-end AND back-end in ONE JAR file. We got away from this years ago, and had 'separation of concerns' which this NOW violates.
I'm more interested in seeing a already done RESTful API on the back-end, one that has API's for JSON an one that has API's for HTML. Then create a SEPARATE front-end, that can call the RESTful UI API's that return the HTML snippets. This would probably ne a nice real-world tutorial. Thanks for the tutorial, it is helpful, but doesn't quite fit what I am looking for.
Hi! I appreciate your thoughts.
The intention of this is not to create a monolithic app. This tutorial shows how you can create a front-end application without using JavaScript.
How you structure your architecture is up to you.
You can have it as monolith, or you can have multiple microservices that serve JSON, and some services will be in charge of serving the UI. The point of this tutorial is to show that a front-end can be written with HTML without using JavaScript.
In the tutorial I’m hardcoding the list of posts that are being printed, but those can come from, and most likely will in a real scenario, a REST API in a different service or even a third party company.
I hope this comment clarifies it.
Thanks for your comment!