HTMX

Pros

• I don't think there's a specific name for it, but it looks like you just invented HTMX
• Treat forms as full-page POSTs by default, then layer htmx/Alpine or your framework on top for live search, conditional fields, etc. If JS dies, users still complete the flow, just with more page loads.
• What is more, the Multi Page Application approach was characterized by less code and fewer dependencies required - overall, it is simply more lightweight. Additionally, tools like HTMX allow MPAs to efficiently handle partial updates, re...
• On HTMX: a very under-sung advantage to using a reactive framework is automatic CSS scoping. With (most) server rendered solutions, you have to leverage something like BEM and/or a utility library to avoid scope collisions.
• Front-end dev has never been better Next.js, Remix, Astro, HTMX, you name it.

Cons

• I love the simplicity of htmx and working with Go on the backend for state. But I've found htmx and working with Go template/templ to get messy very fast.
• The HTMX version seems way more complex to understand and modify.
• HTMX v4 is incorporating some of them (in a larger, less powerful package).