3 ms·
It can be a "backend" the way Python is a "backend". It's the glue, the developer-facing API. The heavy lifting will likely be done by cross-compiling C++ and
by nine_k 5y ago
It can be a "backend" the way Python is a "backend". It's the glue, the developer-facing API.
The heavy lifting will likely be done by cross-compiling C++ and Fortran code to WASM, and expecting it to be JITted, or maybe rewriting portions of in in JS where JIT is already good.
Whoever is first to implement a well-working GPGPU interface in the browser, wins.
- lasagnaphil 5y agoWASM won’t be performant enough for heavy matrix computations because it wouldn’t be able to use SIMD (in its current state). There’s a WASM SIMD proposal in the works but it’s only for 128-bit vectors and I’m not sure it will perform the same as native code.