Implement WebGPU

[tomaka]

cc #10
Link: https://github.com/gpuweb/gpuweb

WebGPU has several advantages:

• It is a more simple standard than Vulkan, but still open source and modern.
• Since it is for the web, it is designed with validation in mind. People should normally not be able to crash a browser by performing malicious API calls.
• It is based around promises, which map well to messages.

[tomaka]

I'm pretty convinced of the right choice being WebGPU, but in terms of libraries it really isn't very mature yet. I also clearly don't want to maintain an entire graphics ecosystem myself.

One thing that's necessary to get started is a way to serialize calls to WebGPU functions (i.e. turn them into some message) and then unserialize them on the other side. The good thing is that this is pretty much a necessity for browsers if they want to call WebGPU functions in a different process, and thus we know that this scheme has to be made possible with WebGPU.

Then ideally the wgpu (https://github.com/gfx-rs/wgpu-rs) library, which is the reference in the Rust world, should be able to call our custom implementation that serializes messages.

[PaperPrototype]

Dude. We need to make this an OS company!

[tomaka]

Another issue is that obviously implementations of WebGPU (or Vulkan, or any other graphics API) that use the native hardware are not going to happen any time soon.

Ideally there should be some way to do software rendering in the WebGPU ecosystem.