The Case for Use.GPU — Acko.net

Reinventing rendering one shader at a time

June 14, 2022 The Case for Use.GPU Reinventing rendering one shader at a time The other day I ran into a perfect example of exactly why GPU programming is so foreign and weird. In this post I will explain why, because it's a microcosm of the issues that lead me to build Use.GPU, a WebGPU rendering meta-framework. What's particularly fun about this post is that I'm pretty sure some seasoned GPU programmers will consider it pure heresy. Not all though. That's how I know it's good. GLTF model , rendered with Use.GPU GLTF A Big Blob of Code The problem I ran into was pretty standard. I have an ima

related reading

• Teaching GPU programming in p5.js: now with compute shaders - Dave Pagurekdavepagurek.com
• General-purpose computing on graphics processing units - Wikipediaen.wikipedia.org
• Thousands of Styled Rectangles in 120FPS on GPU - tchayen.comtchayen.com
• CUDA C++ Programming Guide (Legacy) — CUDA C++ Programming Guidedocs.nvidia.com
• The Best GPUs for Deep Learning in 2023 — An In-depth Analysistimdettmers.com
• BrrrVizbrrrviz.com
• Inside NVIDIA GPUs: Anatomy of high performance matmul kernels - Aleksa Gordićaleksagordic.com
• Why Rendering a Triangle is Complicated | LiamHzliamhz.com
• Gentle introduction to GPUs inner workings | vkSegfaultvksegfault.github.io
• Leveraging Rust and the GPU to render user interfaces at 120 FPS — Zed's Blogzed.dev
• Hello Triangle 🟢 - Learn WebGPU for C++ documentationeliemichel.github.io
• How to Think About GPUs | How To Scale Your Modeljax-ml.github.io