gpuweb
wgpu
Our great sponsors
gpuweb | wgpu | |
---|---|---|
56 | 194 | |
4,565 | 10,846 | |
1.4% | 4.1% | |
9.0 | 9.9 | |
1 day ago | 1 day ago | |
Bikeshed | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
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
wgpu
- 3D and 2D: Testing out my cross-platform graphics engine
- Warp Terminal is now available for Linux
- Linux version of Warp terminal is here
-
Building the DirectX shader compiler better than Microsoft?
And wgpu has been doing this for years. Things like descriptor indexing are not exposed to the web but used by Rust (mostly) engines on native.
-
New Renderers for GTK
If they used https://wgpu.rs/ they would get directx and metal for free (:
-
Show HN: WebGPU Particles Simulation
IIRC it was delayed multiple times. I think the first intent to ship from chrome was before 100 but they kept pushing it off. Firefox still does not support it. There are projects like wgpu[0] that wrap provide a higher level API and I have used some projects using it with no issues. WFIW I didn't see any issue with OP's demo either.
- Deno 1.39: The Return of WebGPU
-
How do I become a graphics programmer? – A guide from AMD Game Engineering team
wgpu, the Rust WebGPU implementation is the bee's knees. https://wgpu.rs/ You can use it beyond the web.
-
There is anything like wgpu.rs for Zig?
There is anything like wgpu.rs for Zig? wgpu.rs is an abstraction on top of Vulkan, Metal, DirectX, etc...
-
New Vulkan Documentation Website
dawn is the WebGPU backend in chromium, while wgpu is the WebGPU backend for firefox written in Rust. wgpu is seeing a lot of use in non-browser uses; there are some examples on their website.
What are some alternatives?
wgsl.vim - WGSL syntax highlight for vim
vulkano - Safe and rich Rust wrapper around the Vulkan API
pyodide - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
noclip.website - A digital museum of video game levels
glow - GL on Whatever: a set of bindings to run GL anywhere and avoid target-specific code
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.
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
wgpu-rs - Rust bindings to wgpu native library
bevy - A refreshingly simple data-driven game engine built in Rust
WASI - WebAssembly System Interface
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.