but wgpu-native is not just webgpu, it runs on top of vulkan, directx12, opengl, etc. no?
but wgpu-native is not just webgpu, it runs on top of vulkan, directx12, opengl, etc. no?
Dor do you use wgpu-native just for the webgpu part?
Lyes, im not sure how thats relavent though
DI mean the readme for silk says
but if you're using webgpu through wgpu-native, does that mean I can also get opengl/directx/metal through wgpu-native when using silk?
providing bindings to popular low-level APIs such as OpenGL, OpenCL, OpenAL, OpenXR, GLFW, SDL, Vulkan, Assimp, WebGPU, and DirectX
but if you're using webgpu through wgpu-native, does that mean I can also get opengl/directx/metal through wgpu-native when using silk?
Lwe just call directly into wgpu-native, so you get whatever they support
Dohh I see, I guess I just find the readme confusing a bit because that means I can get for example vulkan directly, or vulkan through wgpu-native 
but I get it now
but I get it nowLbut the OpenGL/DX/VK in the readme has nothing to do with WebGPU we also bind to those separately
Dyeah that makes sense, but I mean WebGPU and wgpu-native are not the same thing from my understanding? WebGPU is just one of the backends of wgpu-native?
DI guess there's a distinction of "WebGPU the API" and "WebGPU on the web in a browser"
Lwgpu-native is an implementation of the C api of WebGPU
Dand you mean the former while I thought it meant the latter
LWebGPU in the readme refers to the standardized WebGPU C API
Doh right yeah, my confusion is coming from rust I'm basically treating https://github.com/gfx-rs/wgpu (which wgpu-native runs on) as "an API that has multiple backends, webgpu being one of them", but from silk's side this means a different thing
Lyou are thinking about wgpu wrong
Lit does not have a "webgpu backend"
it is the webgpu API
it is the webgpu API
Dyes it is the webgpu API, but on the web it can either run on top of webgl or on top of actual webgpu support in the browser if it's available
Dbut I get it, I didn't realize it was literally the webgpu api itself
DI thought webgpu was just one of its backends, because I'm currently literally using wgpu on top of webgl/vulkan/directx in my projects, and since webgpu wasn't available until basically today (chrome just added it in stable) I didn't think of it that much
Lthe "webgpu backend" is just a shim for emscripten to pass the calls to the JS API, which then pass down through the browser to the C API
Dmakes sense :>
Dthey don't even list it in the architecture diagram heh, I guess more confusion
Kwebgpu is not necessarily the same as wgpu
L^
Kin rust many things are dependent on wgpu, but webgpu is a separate web standard for web apps and that sort of thing
Kalso mentioning servo in that diagram is laughable at best
Lit was kicked off again with funding recently
Kkicked off*
Lyup that is how i spelled it 
Dright, but just to make sure I understand, wgpu-native is the implementation for desktop, then there's browsers that have to do it themselves, and that's basically it? I'd assume wgpu can also run on (as in provide the webgpu API) mobile since vulkan/metal backend?
Kyes? I'm not sure, I'm just saying that wgpu is so good that many rust projects just also use it as an abstraction
Kbut webgpu is largely unrelated
KI mean wgpu is just an implementation detail of webgpu iirc
Lwgpu-native isnt the implementation for desktop, wgpu-core and wgpu-hal is, wgpu-native just provides the agreed upon standard C interface for WebGPU
Lusing wgpu-core
Las kai said wgpu is an implementation detail
Lwe also support Dawn
Lto replace wgpu
Dyou mean unrelated organizationally right? like practically speaking wgpu implements the webgpu API
Kno they are just unrelated
Lunrelated conceptually
Kit's an implementation detail
L^
Kas much as... idk amdgpu and vulkan
Kthey are related as in they are in the same field, but they aren't tied directly to each other
Kthey have an interface where they exchange things
Kbut they are just different things
Kone is an implementation detail of another
Lwebgpu-native is an API
wgpu-native and Dawn are implementers
the projects are not directly related
wgpu-native and Dawn are implementers
the projects are not directly related
Lyou can just swap wgpu-native and Dawn out and ideally everything should still just work in your app
Dmaybe I'm stupid but the wgpu readme literally says "Safe and portable GPU abstraction in Rust, implementing WebGPU API." ... how is it unrelated if it implements the webgpu API
I get that it's rust and not C and you can't swap it out for another webgpu implementation, but like ... "it's the same thing, but in rust?"
I get that it's rust and not C and you can't swap it out for another webgpu implementation, but like ... "it's the same thing, but in rust?"
DI get that it's not direct bindings
