HN Reader

Any word on when it'll be supported on Linux without a flag?

They say:

"This is the next step in the standardization process, and it comes with stronger guarantees of stability and intellectual property protection."

I understand stability, and in the general sense I see that people feel they need to protect their IP, but in this specific case what is meant by "intellectual property protection"?

Honest question: Can someone explain to me why people are excited about WebGPU and WASM and similar technologies?

To me, one of the greatest things about the web is that the DOM is malleable in that you can right click -> view source -> change things. This is dead in an era where the server just sends you a compiled WASM dll.

It seems to me that the inevitable result of things like WASM and WebGPU will be "rich media web 4.0 applications" that are just DRM, crypto miners, and spyware compiled so that they're more difficult to circumvent, and delivered via the browser. An excuse to write web apps with poor performance because "well the user just needs a stronger GPU". It seems like an express train back to the bad old days of every website being written in flash.

I honestly cannot see the upsides of these technologies. Is it gaming? Why would I want to play a 3D game in my fucking browser of all places? That's a strict downgrade in almost every way I can think of. Why would anyone want that? Is it "AI"? Why would I want to run an LLM in the browser, I could just run it natively for better performance?

All I can see and have seen over the last several years is a steady parade of new technologies that will make the internet (and in some cases the lives of every day people) objectively worse while enriching a handful of big tech douchebags.

Why are we going down this path? Who is asking for this stuff? Why the fuck would I want to expose my GPU to a website?

I could use more 2-d line support for CAD applications as well as font drawing.

Being spun off to a different company.

Bindless is pretty much _the_ most important feature we need in WebGPU. Other stuff can be worked around to varying degrees of success, but lack of bindless makes our state changes extremely frequent, which heavily kills performance with how expensive WebGPU makes changing state. The default texture limits without bindless are also way too small for serious applications - just implementing the glTF PBR spec + extensions will blow past them.

I'm really looking forward to getting bindless later down the road, although I expect it to take quite a while.

By the same token, I'm quite surprised that effort is being put into a compatibility mode, when WebGPU is already too old and limiting for a lot of people, and when WebGL(2) is going to have to be maintained by browsers anyways.

I wish there were a good way to profile WebGPU code. I've seen this (very useful) article[1] on setting up PIX, but I'm ambitious. I want to see everything from draw call timings to flamegraphs of shader code.

Right now I feel like the only way to write efficient WebGPU code is to deeply understand specific GPU architectures. I hope some day there's a dev tools tab that shows me I'm spending too much time sampling a texture or there's a lot of contention on my atomic add.

[1]: https://toji.dev/webgpu-profiling/pix.html

Don't know for you but for me the next thing for WebGPU is uninstalling Google Chrome. Manifest v3 my ass.

What's the Firefox compatibility looking like now? Pretty annoying when websites that use it tell you to download and install google chrome.

Whom is WebGPU for, besides Unity?

My team (third party) has developed WebGPU support for Unreal Engine 5, along with an asset-streaming system that solves the large download, multi-gigabyte game in your webpage issue by only loading in what a player needs to see at any given moment. It's constantly loading and unloading data, which helps tremendously with memory management.

WebGPU is going to usher in a new era of web games, the biggest benefit being compute shaders which have never before been possible inside the browser.

DISCLAIMER - Will only work on a Windows device running Chrome or a Chromium browser. Mac and iOS isn't well supported yet.

Space demo - https://play.spacelancers.com/

Forest demo - https://play-dev.simplystream.com/?token=bd4ca6db-522a-4a73-...

I'm curious why supporting ML algorithms is important inside browser ? Will my machine be improperly utilized by the sites I visit ?

Linux support please!