Browser support

[slimsag]

Meta issue related to #21

[guidorice]

(moved my comment from #18 to here)

@slimsag I think it's promising not just for games but for cross-platform graphics of every kind. 👍🏽

Re: "Browser implementation of gpu.Interface", I am curious if you are planning to use Emscripten to build the Javascript <-> WASM glue code? I think that's the only way, currently, because in browser, only Javascript exposes the WebGPU driver.

Also it seems there is definitely interest in using WebGPU for General Purpose GPU (Compute), across native platforms, in browser, and in WASI as well. Some related links, which might provide some ideas for more bespoke things involving shader pipelines etc

• https://tvm.apache.org/2020/05/14/compiling-machine-learning-to-webassembly-and-webgpu
• Use-case for WebGPU with WASI WebAssembly/WASI#285

[guidorice]

Relevant proposal over here: ziglang/zig#10836

[iddev5]

@guidorice you can use freestanding wasm32 and js glue code to access all js resources in zig, no emscripten needed.

See for examples:

1. https://github.com/bootradev/cupcake/
2. https://github.com/masterq32/zero-graphics

[glyh]

Hello! May I ask what's the status of Browser support for now?

[slimsag]

@glyh this is my top priority; before we implement it we need to make sysjs provide bindgen-like capability (#691) which is what I'm working on now.

Once we have that, we should be able to auto-generate browser bindings and then Mach will work seamlessly in the browser.

[mateli]

As a quick and dirty solution can't we utilize emscripten/binaryen? Perhaps by generating a C file for emscripten to compile?