When will WebGPU get enabled by major browsers?
It's been under development for... 5 years now? Chromium and Firefox carry a development preview behind a flag.
https://caniuse.com/webgpu
When will WebGPU get enabled by major browsers?
It's been under development for... 5 years now? Chromium and Firefox carry a development preview behind a flag.
https://caniuse.com/webgpu
@codewiz They're still making changes to WGSL's syntax. I expect it'll be a while more before it's ready.
@wizzwizz4 Ohh... 😔
But I guess it's for the better... hopefully this will be *the* shading language that works across all GPU vendors and operating systems.
@wizzwizz4 GLSL looked a lot like C with a nice syntax for vector and matrix operations.
WGSL is looking more and more like Rust with less syntactic noise.
Too bad statements such as switch and if don't return values like in Rust. I think the typical code that goes into shaders would benefit from a slightly more functional style. And I say "slightly" because it can be abused to write every function as one big expression.
@codewiz I do prefer the new WGSL syntax. It's got @attribute instead of [[attribute]] syntax.
@codewiz WGSL is not a very high-level language, and it's supposed to be approachable. "Everything is an expression" is a nice language feature, but it's not an obvious one for a C or English speaker.
WGSL isn't particularly better than GLSL, imo, except in its explicitness. GLSL has a load of hidden default state; not being an OpenGL expert, I don't know what the defaults are or how to change the options. But with WGSL, I can read a shader and understand it, and I've got search terms if not.
Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.