HTMX: Why You Don't Always Need a SPA Framework
summary
Argues that HTMX plus a hypermedia pattern often replaces a SPA for CRUD sites, showing a 1,000‑user nutrition app migrated from Angular to server‑rendered HTML with htmx attributes. Demo uses hx-post, hx-delete, hx-target, hx-swap, server‑side validation via out‑of‑band swaps, and small custom elements as glue. htmx is ~14–16 KB gzipped; example web components run 2–3 KB each; the demos mostly work live with a few minor edits.
AI-written summary · about
chapters (10)
- 0:00HTMX and hypermedia intro
- 1:48What HTMX is and how it works
- 7:27HTMX vs single-page applications
- 15:31Progressive enhancement
- 29:11When to use HTMX
- 35:53Form validation and swaps
- 43:06Debugging HTMX
- 46:08Glue code needed
- 49:02Web components with HTMX
- 55:49HTMX future
related talks
49mBring back the joy in web development with HTMX and Hypermedia-Driven Applications
27mHTMX – Say “no” to Complexity
13mHTMX - simplicity in frontend development
54mHTMX: Web 1.0 with web 2.0 benefits without the grift of 3.0
01h 02mThird Way Web Development
26mReimagining dynamic web apps with HTMX
23mIntroduction to server-driven web applications using htmx
19mhtmx: Writing JavaScript to Avoid Writing JavaScript