wgpu-native
gpuweb
wgpu-native | gpuweb | |
---|---|---|
13 | 56 | |
737 | 4,580 | |
4.8% | 1.0% | |
8.1 | 9.1 | |
1 day ago | 7 days ago | |
Rust | Bikeshed | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wgpu-native
-
Capturing the WebGPU Ecosystem
The Mach engine project has prebuilt Dawn libraries and also a simplified build-from-source process using the Zig build system, see:
https://machengine.org/pkg/mach-gpu-dawn/
It's also possible to use wgpu-native in C/C++ projects as prebuilt library, see:
https://github.com/gfx-rs/wgpu-native
-
I started drafting a tuto to learn WebGPU for native C++
It is based on the wgpu-native implementation (Firefox backend) but I plan on adding a receipe for using it with Dawn (Chrome backend) as well.
- How is Vulkan supposed to supersede OpenGL in practice?
- Vulkan update: version 1.2 conformance for Raspberry Pi 4
- New open source Common Lisp 3D graphics project -- call for participation
-
Go bindings for WebGPU
go-webgpu provides binding for wgpu-native (a safe and portable GPU abstraction in Rust, implementing WebGPU API).
-
The current state of GPU API's and why I wish V-EZ hadn't died.
Rust, C++
-
WebGL 2.0 is Now Supported in All Major Browsers
When you look at graphics APIs in Rust practically everything is pointing towards, and telling you to use, wgpu, which abstracts over Vulkan, Metal, DX11/12, GLES and WebGPU and is based on, drumroll, WebGPU. Hardly surprising as it's the backend firefox is going to use. And yes it has a C API, too.
-
Mach Engine: The future of graphics (with Zig)
Probably the easiest option would be to target wgpu-native prebuilt binaries but these don't have iOS/Android (unsure if wgpu-native supports iOS/Android at all)
-
Learn Wgpu
WGPU is the underlying implementation for WebGPU in Firefox and it has C bindings: https://github.com/gfx-rs/wgpu-native.git.
gpuweb
- WGSL Is Terrible
-
WebGPU now available for testing in Safari Technology Preview
People keep spreading this incredibly misleading statement, and yours is even more misleading (suggesting Apple opposed a 'GPU WASM')
By all accounts, Apple's /only/ stance was that if WebGPU used SPIR-V it would be a non-starter for them, due to ongoing legal issues between Apple and Khronos.
Apple actually proposed WebHLSL in collaboration with Microsoft, to have HLSL be the standard.
Mozilla employee's stance[0] was that SPIRV was too low level, did not fit with the goals of WebGPU portability and security, and expressed concern that Khronos may add functionality to SPIRV they cannot support in WebGPU like raytracing instructions .. 'So we'd always be on the verge of forking SPIR-V in some way.'
It was also noted by many people that even if a bytecode format was used, it would still have to be translated to the target (HLSL/DXIL, MSL, etc.) in almost the same way a text format would.
Nobody proposed a 'GPU WASM equivalent' or an alternative bytecode format.
The hard truth is that shader compilation is a fucking nightmare, people do not realize how bad it is across the different native APIs. SPIR-V is good, but it doesn't solve that - and presents other challenges if you are a web browser API. Vulkan and SPIRV are not the golden goose many make them out to be.
[0] https://github.com/gpuweb/gpuweb/issues/847#issuecomment-642...
-
Show HN: WebGPU Particles Simulation
Yes it is still a bit new. WebGPU is not finished and is still being worked on: https://webgpu.io/
-
Capturing the WebGPU Ecosystem
WebGPU currently doesn't support the "bindless" resource access model (see: https://github.com/gpuweb/gpuweb/issues/380).
The "max number of sampled texture per shader stage" is a runtime device limit, and the minimal value for that seems to be 16. So texture atlasses are still a thing in WebGPU.
-
Why aren't we using highly efficient int8 calcualtions in quants? (maybe eli14?)
There's even an implementation under discussion to have the dp4a instruction added to WebGPU (https://github.com/gpuweb/gpuweb/issues/2677)
- WebGPU – All of the cores, none of the canvas
- How to get Chromium working with the Vulkan driver on a RPi4?
- Anyone has Chromium WebGPU working?
- [Rust_Gamedev] WGSL est-il un bon choix?
- I want to talk about WebGPU
What are some alternatives?
go-webgpu - Go bindings for WebGPU, a safe & cross-platform GPU abstraction
wgsl.vim - WGSL syntax highlight for vim
webgpu-headers
pyodide - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly
learn-wgpu - Guide for using gfx-rs's wgpu library.
noclip.website - A digital museum of video game levels
wgpu - Cross-platform, safe, pure-rust graphics api.
BestBuy-GPU-Bot - BestBuy Bot is an Add to cart and Auto Checkout Bot. This auto buying bot can search the item repeatedly on the ITEM page using one keyword. Once the desired item is available it can add to cart and checkout very fast. This auto purchasing BestBuy Bot can work on Firefox Browser so it can run in all Operating Systems. It can run for multiple items simultaneously.
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.
wgpu-rs - Rust bindings to wgpu native library
angle - A conformant OpenGL ES implementation for Windows, Mac, Linux, iOS and Android.
WASI - WebAssembly System Interface