So you want a modern frontend for your Python web app?
summary
Shows that replacing a heavy SPA stack (React + Redux + DRF) with server‑rendered Django plus HTMX and AlpineJS delivers concrete gains: the codebase shrunk significantly, deployment and testing simplify, pages load on slow devices, and junior engineers become productive as full‑stack contributors. Demoed patterns include swapping HTML partials over XHR, minimal client state, and HTMX + websockets for realtime. Tradeoffs noted: harder client state management and denser HTML (Tailwind + attributes) but big wins for developer velocity and user performance.
AI-written summary · about
chapters (7)
- 0:00Introduction and history
- 3:15Speaker introduction
- 9:53Introducing HTMX and AlpineJS
- 13:25HTMX vs React comparison
- 15:32Real-world HTMX adoption story
- 18:20Organizational benefits of simplicity
- 20:10Closing and resources
related talks
40mDjango & JavaScript: A long and complicated friendship
26mUsing Django 4.2's StreamingHttpResponse and HTMX SSE to provide real time notifications
37mPerformant Django
40mAsyncio Stack & React.js or Development on the Edge
47mPython on the Client Side Web
38mDjango Rest Framework + Redux
41mDash: data exploration web apps in pure Python
31mReinventing Django for the Real-Time Web