I would think you can achieve similar speed using WebGL in the browser and then have all the comfortable functionality of the browser for free.
I would think you can achieve similar speed using WebGL in the browser and then have all the comfortable functionality of the browser for free.
For the web, you have no choice but to use WebGL.
If you're interested on why a Vulkan binding for the web is not a good idea, I found this doc (from two engineers working at Google) quite interesting : https://docs.google.com/document/d/1-lAvR9GXaNJiqUIpm3N2XuGU...
Definitely, having some form of GPGPU on the web is the next step. It is currently one of my few complaint with WebGL: The lack of compute shader.
There are existing GPGPU things running on WebGL, see eg https://github.com/tensorflow/tfjs-core and https://magenta.tensorflow.org/demos/#web-apps
I hope not. The proposed standard was not even remotely vendor-neutral.
I would love to have compute shaders in WebGL. All it would require is bumping the OpenGL version that WebGL is based on from ES 3.0 to ES 3.1 in the next revision.
As far as I can tell, that will not happen because it would reduce the need for the WebGPU proposal. Needless to say, I find the situation very annoying.
Why not? WebGPU work continues here, based on the work that Apple proposed. Google has a cross-platform prototype implementation. https://github.com/gpuweb/gpuweb
> I would love to have compute shaders in WebGL. All it would require is bumping the OpenGL version that WebGL is based on from ES 3.0 to ES 3.1 in the next revision.
WebGL2 has very little vendor support already, and OpenGL is a dead end, from an API perspective. Something low-ish like Metal without being as absurd as Vulkan would be a great fit for the web.