HTML-ivating your Django web app's experience with HTMX, AlpineJS, and streaming HTML
summary
Shows a concrete claim: you can get SPA‑like responsiveness without a SPA by combining HTMX, AlpineJS, and streaming HTML from Django. Presents a working demo app that loads in 20 seconds versus competitors at 59 seconds and a production site at ~4 minutes, and cites archive data where half of React sites take >10s and 10% take >25s. Describes implemented techniques — template splitting, streaming fragments, and server-sent events — and measures that these reduce time to interactive and cut client JavaScript and payload budgets.
AI-written summary · about
chapters (18)
- 0:00Welcome
- 1:03The limitations of single-page applications
- 4:32Faster alternative example
- 10:17HTMX and AlpineJS intro
- 12:46Traditional HTML benefits
- 15:15HTMX partial updates
- 15:59AlpineJS interactions
- 17:00HTML attributes for DX
- 18:23Community testimonials
- 20:08SPA performance costs
- 23:16Perceived speed priority
- 24:20Streaming HTML benefits
- 27:31GitHub’s streaming pattern
- 28:14Streaming in Django
- 30:01Template splitting for streaming
- 32:30HTMX server-sent events
- 36:24Open-source resources
- 36:47Key takeaways
related talks
26mModern web apps with (almost) no JS: Enhancing UX with HTMX in Django
26mReimagining dynamic web apps with HTMX
35mJavascript Fatigue: Back to Hypermedia w/ Django+HTMX
49mBring back the joy in web development with HTMX and Hypermedia-Driven Applications
23mIntroduction to server-driven web applications using htmx
41mRapid server side full stack web development with ViewComponents and htmx
02h 26mWeb Development With A Python-backed Frontend: Featuring HTMX and Tailwind
48mClientside templates for reactive UI