aevaFeb 20
opengl is for people who want to finish projects and vulkan is for people who are just looking for something to help their ecs framework stand out a little more
Show threadhalcy​ Feb 20

@aeva to be entirely fair, after finishing (1 week to release! basically done!) a project with opengles3.0 just now, I can see why people would want to use vulkan instead, but likely that's just because I have not used vulkan enough

wait actually. more like i can see why people would want to use webgpu instead. where does webgpu fall in this spectrum

Show threadaeva
@halcy falls into the "weird rust thing i don't care about" bin
Feb 20 at 10:04amWeb
Show threadhalcy​ Feb 20
@aeva wait, it's.... usable from C++ or really wherever, isn't it. i thought it was, at least. the main reason I'm curious about it at all is that SDL3 added support for creating contexts for it and that's very not rust unless something changed while I wasn't looking
Show threadradgeRaydenFeb 20
@halcy @aeva trying to get dawn to build is harder than writing the renderer.
Show threadhalcy​ Feb 20

@radgeRayden well, I am mostly interested in running shit in the browser via emscripten -> sdl3 for context -> render a bunch of stuff

in which case I think something like dawn, is not needed?

Show threadradgeRaydenFeb 20
@halcy yeah if you want web it should be easier. Though the support situation is not good yet - for example I don't think any of the browsers shipped linux support.
Show threadhalcy​ Feb 20

@radgeRayden oof

yeah I guess the initial decision for opengl over webgpu was motivated a lot by familiarity with the API, but also by "wouldn't it be nice if people could actually run this", and I haven't really checked whether this has changed

Show threadradgeRaydenFeb 20
@halcy I'm the guy in the picture (I'm writing vulkan code) and I think if I actually ship something it might be necessary to write an opengl fallback, yeah. In my case the choice of the less backwards compatible API is wanting to use some cool new things.
Show threadaevaFeb 20
@radgeRayden @halcy i don't think I've seen webgpu work yet in Firefox at all. webgpu is a total joke
Show threadradgeRaydenFeb 20
@halcy @aeva on the rust note: wgpu (the rust version) has wgpu-native that targets the common C header. It's currently lagging behind due to lack of manpower, but it exists.
Show threadaevaFeb 20
@radgeRayden @halcy the rust frog boiling shader language and lack of required support for spirv is a bridge too far for me. i will not use it ever until that changes.
Show threadaevaFeb 20
@radgeRayden @halcy the standard could have been good but it's still born
Show threadredstrateFeb 20
@aeva @radgeRayden @halcy the only true opinion about webgpu. when i last looked there was some SPIRV->WLSL (or whatever they call it) bridge but it was super annoying to integrate. that's when i reach for something more sane
Show threadaevaFeb 20
@redstrate @radgeRayden @halcy I suppose compiling from a high level language to an IR back to a high level language only for the runtime to presumably compile it back into an IR before passing it off to the driver to compile to the final binary is better than nothing, even if it's completely ridiculous.
Show threadhalcy​ Feb 21
@aeva @redstrate @radgeRayden i have no well formed opinion on this but I think „spirv“ sounds funny so clearly it’s good. It’s like the tinny sound an old car on its last legs makes. Spirvspirvspirvspirv
Show threadaevaFeb 21
@halcy @redstrate @radgeRayden spirv has the superior mouthfeel for sure