Your Browser Is a Compute Platform (And You’re Using It for Forms)
Annotation
Most frontend performance discussions focus on micro-optimizations: reducing re-renders, tweaking bundles, shaving milliseconds off execution time. But in many cases, the real problem isn’t how we write code. It’s where we run it.
Modern browsers are no longer just UI layers. They give us access to both CPU and GPU, allowing us to run compiled code via WebAssembly and massively parallel workloads via WebGPU. And yet, most applications still treat the browser as if it were limited to forms and dashboards.
In this talk, I’ll walk through a live demo that explores what happens when we shift the execution model. We’ll compare JavaScript, WebAssembly, and WebGPU on the same problem, and see performance differences that go far beyond typical optimizations.
This is not a talk about replacing JavaScript. It’s about understanding when traditional approaches stop scaling, and how to choose the right execution layer when they do.
Because sometimes, your app isn’t slow.
You’re just running it in the wrong place.
