Meta issue on Pyodide support #846

We have two approaches:

Via JS/Pyodide calls

Use WebGPU directly through JS. Also relies on Pyodide.

• pure python js_webgpu backend using pyodide #753
• Well in progress.
• Stuck on some stack switching mechanics related to async.

Via wgpu

Rely on wgpu's mechanics to call out to WebGPU via JS.

• Requires Emscripten 6.0.10
• Requires us to create a backend based on a wgpu as a compiled extension module
• Needs some work at wgpu
  • Fix support for Emscripten (v6.0.10+) by making it use web-sys gfx-rs/wgpu#10515
• And at wasm-bindgen to support stratic linking
  • fix: make Emscripten side-module bindings callable wasm-bindgen/wasm-bindgen#5326
• Pyodide target's an earlier Emscripten.
  • Support for Emscripten 6.0.10 / wasm-bindgen pyodide/pyodide#6476
  • Tiny chance they bump it for py315
  • Otherwise we wait for py316 (summer/fall 2027)

Notes on PyJS

cc @Alex-PLACET

PyJS is a novel approach to compile typed Python to JS.

• Backend could follow same path as the JS/Pyodide path, but then we have yet another backend.
• Backend via Emscripten seems feasible.