HTMX vs WASM - more backend or more frontend?
summary
Compares two concrete approaches: running Python in-browser with Pyodide and PyScript demos (pip-install numpy/pandas in the browser, VM RAM ~4GB limit, big libs cause multi-second loads) versus HTML-first interactivity with HTMX with Django task demo (hx- attributes, CSRF integration, server views return HTML fragments, dynamic add/delete without custom JavaScript). Claims JavaScript becomes “low-level” rather than required; demos show PyScript works but is heavy, HTMX is lightweight and fast — choose by payload and UX needs.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:30Project Iodine and Pyodide background
- 6:09How WebAssembly runs Python in browser
- 10:40PyScript framework overview
- 14:57HTMX introduction and Django integration
- 18:12Live demo of HTMX with Django
- 22:03Future of frontend development trends
- 25:11Closing and PyCon CZ plug
- 25:35Q&A session
related talks
26mModern web apps with (almost) no JS: Enhancing UX with HTMX in Django
26mReimagining dynamic web apps with HTMX
37mHTMX: Frontend Revolution
35mJavascript Fatigue: Back to Hypermedia w/ Django+HTMX
23mIntroduction to server-driven web applications using htmx
24mBack to the Future of Hypermedia in Django
54mHTMX: Web 1.0 with web 2.0 benefits without the grift of 3.0
47mHTMX, or the return of AJAX in Web development