Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
A discussion that caught my eye (an old one, but not that old) raised some pretty bad issues in WGSL which make me wonder:
I have been following u/sotrh tutorial (which might I add is amazing, thank you) and have reached the point where shaders come into play.
My recommendation is to stick with WGSL for wgpu. I have some simple compute shaders examples if you wanna check out.
P.S. I'm fully using WGSL in vange-rs and baryon
P.S. I'm fully using WGSL in vange-rs and baryon
As someone who as used both in the past and contributes to a pure rust shader translator (naga, it's what wgpu uses) .
IIRC, somebody looked at it, but nothing usable yet. There is, however, cargo-wgsl, vscode-wgsl, Emacs plugin, and Vim plugin
IIRC, somebody looked at it, but nothing usable yet. There is, however, cargo-wgsl, vscode-wgsl, Emacs plugin, and Vim plugin
IIRC, somebody looked at it, but nothing usable yet. There is, however, cargo-wgsl, vscode-wgsl, Emacs plugin, and Vim plugin