gpuweb
simple-game
Our great sponsors
gpuweb | simple-game | |
---|---|---|
56 | 4 | |
4,565 | 5 | |
1.4% | - | |
9.0 | 6.6 | |
7 days ago | 3 months ago | |
Bikeshed | Rust | |
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.
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
simple-game
-
Looking for an image manipulation library that can add text to images. (and has documentation for it)
I have a somewhat naive version of this sort of system running via wgpu, but that's likely lower level than you'd want to go.
-
Some advice on starting out
I won't claim this is great code, but poke around a little bit at my wgpu code and get a sense for how it compares to OpenGL. Overall the concepts are pretty close to each other, it's just that you declare everything up front instead of poking at OpenGL via functions to set things to the state you want.
-
First Public Working Drafts: WebGPU and WebGPU Shading Language
It's really not that bad. I had some complaints about WGSL a few months ago but it was surprising how quickly it improved. Here are some simple real-world shaders you can look at:
https://github.com/bschwind/simple-game/tree/9de179085a04dd4...
If you combine it with a quick build step to give you shader compilation errors before your program runs, it becomes a pretty nice shading language. There are still a few rough edges but it's not _that_ bad to work with.
-
Last big wgpu-rs example shaders are fully ported to WGSL now, and validated in it
Thanks! I ended up going that route here
What are some alternatives?
wgsl.vim - WGSL syntax highlight for vim
nannou - A Creative Coding Framework for Rust.
pyodide - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly
wgpu-rs - Rust bindings to wgpu native library
noclip.website - A digital museum of video game levels
sokol - minimal cross-platform standalone C headers
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.
imageproc (PistonDevelopers) - Image processing operations
piet - An abstraction for 2D graphics.
WASI - WebAssembly System Interface
naga - Universal shader translation in Rust