11–20 of 55 posts
Earlier quoted context omitted.
So you're telling me you write Java professionally?
Funnily enough, in a world with WASM, we might actually have Java in the backend and C in the frontend rather than vice versa as it would've been likelier in the 90s.
Go is just Java without the WM.
Rust is just a native compiler that creates slow programs and complains a lot.
You absolutely cannot implement stream compaction “at the speed of native” as WebGPU is missing the wave/subgroup intrinsics and globally coherent memory necessary to do that efficiently as possible.
You absolutely cannot implement stream compaction “at the speed of native” as WebGPU is missing the wave/subgroup intrinsics and globally coherent memory necessary to do that efficiently as possible.
Oh look it's subgroup support landing last week: https://github.com/gfx-rs/wgpu/pull/5301
https://github.com/gpuweb/gpuweb/blob/main/proposals/subgrou...
There is a proposal for supporting subgroups in WebGPU proper but it's still in the draft stage.
Isn't it 1s1 in the ground state so the probability distribution would look like a sphere.
Hmm, why does the hydrogen atom look like a d orbital? Isn't it 1s1 in the ground state so the probability distribution would look like a sphere.
Earlier quoted context omitted.
Oh look it's subgroup support landing last week: https://github.com/gfx-rs/wgpu/pull/5301
That's a wgpu-specific extension, not part of the actual WebGPU spec, so you can't use it on the web. https://github.com/gpuweb/gpuweb/blob/main/proposals/subgrou... There is a proposal for supporting subgroups in WebGPU proper but it's still in the draft stage.
The `wgpu` implementation linked will make its way into Firefox eventually. Dawn will follow up with a similar one for Chrome.
I was linking it to demonstrate there are no technical hurdles and it's only really approval remaining.
You absolutely cannot implement stream compaction “at the speed of native” as WebGPU is missing the wave/subgroup intrinsics and globally coherent memory necessary to do that efficiently as possible.
Oh look it's subgroup support landing last week: https://github.com/gfx-rs/wgpu/pull/5301
You absolutely cannot implement stream compaction “at the speed of native” as WebGPU is missing the wave/subgroup intrinsics and globally coherent memory necessary to do that efficiently as possible.
This is the eternal browserbros. attempt to make us think native has zero value now that we have a completely captured and bloated browser. The browser is dead, the only thing you can use it for is filling out HTML forms and maybe some light inventory management. The final app is C+Java where you put the right stuff where it is needed. Just like the browser used to be before Oracle did it's magic on the applet.
Yea. Nah!
That obit is a bit premature
Earlier quoted context omitted.
Funnily enough, in a world with WASM, we might actually have Java in the backend and C in the frontend rather than vice versa as it would've been likelier in the 90s.
WASM is adding GC... recreating the wheel of the applet but without escaping the problem of javascript glue. Go is just Java without the WM. Rust is just a native compiler that creates slow programs and complains a lot.
Good morning Troll
I'll give you "complains a lot."