What's Next for WebGPU

Original Article ↗ Hacker News Discussion ↗

Adoption, Platforms & Ecosystem

  • WebGPU is supported in Chrome and (behind a flag) Safari; Linux and many Android GPUs lag, which frustrates some developers who see it as “Windows‑only for now.”
  • Safari’s implementation is reported as spec‑compliant and built on Metal; Apple was heavily involved in the spec, so some argue it’s unlikely they’ll abandon it.
  • Others are skeptical, citing Apple’s history: weak WebGL2/texture support, no Vulkan, no WebXR, WASM breakages, and fear of an “Apple-flavored” WebGPU.
  • Firefox is still working toward full support; WebGPU and Rust’s wgpu library are related but distinct (spec vs. implementation).

Who WebGPU Is For

  • Use cases mentioned: game engines (Unity, Unreal, Bevy, Construct, Godot), web CAD / mapping, video editors, ML/compute (e.g., local analysis in a browser without uploading data), and large apps like Google Maps.
  • Some argue WebGPU + WASM allow one codebase (Rust/C#/etc.) to target desktop and browser.
  • Others say many 2D games or non‑intensive apps don’t need WebGPU/compute shaders and should stick to WebGL/Canvas or native engines.

Security, Sandboxing & Misuse

  • Concern: exposing GPUs and compute shaders will enable crypto miners, tracking, and heavier spyware.
  • Counterpoint: GPU usage is still sandboxed (like JS), browser settings/extensions can disable it, and local compute can improve privacy vs. server‑side ML.
  • Some propose permissions or prompts when sites want heavy ML/compute, similar to camera/mic.

Performance, Features & Rust Ecosystem

  • A major technical theme is the absence of “bindless” resources in core WebGPU. Developers say this makes state changes expensive and texture limits tight, hurting high‑end rendering and GPU‑driven techniques.
  • There is an active bindless proposal, but it’s early and might land years out; some worry WebGPU is already constrained by 10‑year‑old hardware and browser safety.
  • Rust graphics (wgpu, Bevy, others) benefit from WebGPU but are constrained by its “lowest common denominator” design; debate over whether wgpu’s priorities (correctness/compat vs. performance) are right.
  • Some highlight significant wgpu performance work; others cite regressions and frustration.

Tooling & Developer Experience

  • Developers want much better profiling and debugging: draw-call timings, shader flamegraphs, easier GPU introspection.
  • Current options involve vendor tools (PIX, Nsight, Xcode) and timestamp queries; Web‑integrated tools are seen as immature.
  • General sentiment: powerful but complex; success will depend on better tooling and broader, stable platform support.