Chrome 113 with WebGPU breaks GPU.js about gpu.js HOT 12 OPEN

Yea I'll have to address it soon. Perhaps next week.

from gpu.js.

Nevermind; renamed all "GPU" instances in gpu-browser.min to "GPUX" That worked for now.

from gpu.js.

Same.
is there a quick fix / hack?

from gpu.js.

Nevermind; renamed all "GPU" instances in gpu-browser.min to "GPUX" That worked for now.

Me to, but thats a very bad practice.... thats a temp solution not a permanent one

from gpu.js.

Oh, yes, bad practice indeed. "Dont try this at home" Consider it a workaround until a better solution is implemented.

from gpu.js.

@robertleeplummerjr can you fix this?
all the cool gpu.js projects suddenly stopped working :p

from gpu.js.

maybe gpu.js can leverage WebGPU?
if it has any advantages performance-wise, and if the effort required doesn't mean rewriting all of gpu.js

would be especially interesting to see if it allows more flexibility with data types passed to/returned by gpu.js

from gpu.js.

yeah that will be awesome!

from gpu.js.

We'd love to do that, but the existing API isn't mature enough across browsers, at least from what I've seen with compute capabilities. I've never had a stock example actually run and have a means of starting to upgrade GPU.js to that.

As far as the issue with GPU being overwritten (rude with prejudice) what do you guys think of using GPUJS for browser only, and GPU everywhere else (node, typescript, etc.)?

from gpu.js.

sounds good enough

from gpu.js.

We'd love to do that, but the existing API isn't mature enough across browsers, The api is very VERY mature, but only a few browsers support it https://caniuse.com/?search=webgpu

from gpu.js.

As I have looked at gpu.js code vs current webgpu surface, it will be largely obsoleted, as gpu.js has to deal with how webgl handles concurrency, there is no such problem in webgpu, so I think its better to totally start from scratch (keep the brand name if you must, but from scratch you must start)

from gpu.js.