From Graveyard to Glory: Production Python in the Browser
summary
Claims a production SPA ships a full Python runtime to the browser using Pyodide and WebAssembly, ties business logic into a Svelte UI compiled with Svelte + Vite + Comlink for typed RPC to a Python web worker, and leverages Pydantic+OpenAPI for TypeScript safety. Reality check: production needs Playwright CI tests, telemetry via a server tunnel to Sentry/PostHog, package wheels (WebAssembly wheels on PyPI), a state machine and SharedArrayBuffer interrupts; real apps (FinFam, Glumppad) see ~6–7s engine startup but then work.
AI-written summary · about
chapters (13)
- 0:00Python in the browser
- 1:55Agent missed critical gaps
- 2:38Past Python-in-browser attempts
- 7:13Piodide and WebAssembly
- 9:18Glumppad vs production apps
- 10:22Gaps in agent-built apps
- 13:10Production architecture
- 14:34Piodide future
- 15:41Edge computing with Cloudflare
- 16:22Verifiability and Python
- 18:51Python for agent-assisted humans
- 19:54Resources and closing
- 20:19Q&A
related talks
02h 55mWriting Serverless Python Web Apps with PyScript
01h 39mPyScript - Writing a Python application in the browser
45mThe marvelous world of Python in Browser: a nice surprise
39mPyScript - Python in the Browser
45mHow to run Python in the browser
28mPython Apps in the Browser made simple by PyCafe
47mPython on the Client Side Web
42mJoyful Pyodide with...tests?