webgpu VS gpu.js

I think your reached dead status partially for being a new account but on the off chance you're a new account legitimately wondering why your comment got downvoted so quickly:

It's compatible with both web and Node. In node it uses https://github.com/stackgl/headless-gl to provide Node with a WebGL compatible implementation as Node doesn't ship with GPU access out of the box. They are looking into https://github.com/maierfelix/webgpu or similar which instead provides Node with a WebGPU compatible implementation. Both require N-API. The tracking issue can be found here for reference https://github.com/gpujs/gpu.js/issues/507.

You might already be familiar, but a GPU.js backend can provide some speedups via good old WebGL -- no need for WebGPU just yet!

[0]: https://github.com/gpujs/gpu.js/

Very cool project.

I learned WebGL three years ago but before I dove into the underlying concepts I used GPU.js [1] to quickly prototype my project. Eventually, the abstraction prevented necessary performance optimizations so I switched to vanilla GLSL and these vanilla GLSL "shaders" were initially ejected from GPU.js.

Writing JS code then looking at the generated WebGPU output is a great way to get familiar with WebGPU. Thanks for this.

[1] https://github.com/gpujs/gpu.js/

I used this library on my project but I think it's no longer maintained. I PRed a fix for buggy atan2 over a year ago and no movement [1]. I do highly recommend it if you're a web developer interested in harnessing parallel processing.

[1] https://github.com/gpujs/gpu.js/pull/683

Thanks for pointing this out. I've submitted a PR to resolve this: https://github.com/gpujs/gpu.js/issues/757

That being said, if you're not building from source (you're running an LTS version of node on a supported platform), you don't need to worry about python or many of the build deps.