HTMX is amazing! 

+1

Yup, and I feel like the go course is lacking some stuff and node course is kinda chaotic and not as simple as go. Just my thought

No, most servers probably have compression turned on, such as gzip,, making any difference negligible

But yeah, it was Dan that also said RSCs work similar to HTMX. " rsc is htmx with components on both sides." I would post links but you can't on RU-vid.

I'm sorry - once I got a bit more time (don't know when that will be the case though....) I do plan to improve the video background.

@@maximilian-schwarzmueller all good my friend. Just joking around. Great video btw, thank you.

React is OVER used

I would say 90% of react sites could be migrated to HTMX. And with that simplify code bases by a ton. Amazing technology.

It seems like you chose bad tech for your project. Highly interactive apps without data fetching aren't for HTMX. Additionally maybe your backend tech isn't good fit for project or isn't working well with HTMX. I don't know the details, but you cannot blame tech for being wrongly used. For me HTMX solves problem with state synchronization, but makes network traffic bigger, so highly interactive apps aren't good fit for it. You can mix some od your js with it. I didn't try, but I heard AlpineJS is a complementory soluction for interactivity for HTMX.

The keywords in your comment "round trips to the server". And almost nobody speak about it. It makes this tech not a viable solution for me.

@@fsharplove What kind of rendering are you using? Cause making SSR or SSG is almost the same as HTMX. All of them involve asking server for some data to render. Additionally when your SPA application have spinners for loading data after the page is loaded is exactly what HTMX does under the hood, but in first case you have json and in second pure html being sent. This tech isn't that scary, if you know how and when to use it. If you need a lot of reactivity, which doesn't need anything from server HTMX isn't for you. But when you need just to fetch some data and dispay it and navigate through it, then HTMX is perfect for you.

@@Quxer0721 I started with pure WASM SPA AOT (plus a WEB API for data) before .NET 8 was released. Now, I am considering SSR + WASM AOT. I use a lot of CPU and don't want to rely heavy on network connection. I want to use the CPU of the client instead of some cloud services that will cost me a lot of money. I have never ever considered what is called today Interactive mode Server.

@@Quxer0721 I was using Blazor WASM AOT SPA with a minimal WEB API and SQLite for data. I was reluctant to use the new .NET8 stuff but now I plan to go to the route SSR + Blazor WASM AOT. The application I am building using a lot of CPU, and reactivity, I feel it's the best combo. I tend to prefer client side execution and avoid network dependencies. AOT is used for two purposes: enhance performance. Avoid code decompilation. But I have to test this (especially the AOT aspect) because for now I have released nothing, 😁. And you have Blazor MAUI as a bonus for "native" apps with better performance than WASM.😁😁

You should always sanitize user input