Why HTMX is crushing React, Vue & Svelte
summary
Claims that HTMX removes JSON APIs, virtual DOM and extra deployments and shows a working e‑commerce demo built with Kotlin + Spring Boot and plain Tailwind. The app sends and returns HTMX partial HTML so the server renders view models, a typed backend powers a live search (input-triggered, 200ms debounce) that updates only the product list, and an basket counter increments via HTMX-triggered header events — no SPA framework, no full page reloads, and templates rendered with JTE.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:00Hotwire and HTMX rise
- 6:16SPA defaults problems
- 11:35Simpler frontend use cases
- 15:06HTMX partial reloading
- 17:20HTMX traction reasons
- 18:25Live demo setup
- 22:35HTML in controllers
- 25:55Full-page reloads demo
- 27:22Adding HTMX interactivity
- 30:36Live search with HTMX
- 33:49Debounce for live search
- 34:53Basket count update
- 37:04Final demo and Q&A
- 37:46HTMX multi-team benefits
related talks
26mReimagining dynamic web apps with HTMX
49mBring back the joy in web development with HTMX and Hypermedia-Driven Applications
27mHTMX – Say “no” to Complexity
37mHTMX: Frontend Revolution
57mBuilding dynamic web apps with Kotlin, WebComponents and Htmx
47mHTMX, or the return of AJAX in Web development
54mHTMX: Web 1.0 with web 2.0 benefits without the grift of 3.0
57mHTMX: Why You Don't Always Need a SPA Framework