tojiro

tojiro, 3 days ago

@mcc The game was absolutely brilliant, though I feel like it would really show it's age if you went back and played it today.

But you should at least watch the into cutscene! It's very 90s and goes harder than a 640x480 video has any right to.

https://www.youtube.com/watch?v=ws1hamUjm68

tojiro, 5 days ago

Both of these APIs report whatever the browser feels comfortable divulging about your GPU without any additional permissions. For Chrome this is typically the GPU vendor and a broad architectural family (eg: "nvidia" "turing") but not a specific model or driver version. Other browsers may choose to abstract these further or not report anything at all.

tojiro, 5 days ago

The original intent behind requestAdapterInfo() was to allow a second tier of information, where you could specifically request more details about the GPU (like a model number) and the user would get a permission prompt asking if they were OK with that. This was aimed at things like filing a bug report with a web app dev, where they could ask if you wanted to provide more GPU details to help with their debugging.

tojiro, 5 days ago

As the various vendors started implementing the API, though, it became apparent that some vendors would never request that permission, and even those that wanted to struggled to find a way to communicate what was being requested to your standard users. So the idea of requesting the second tier of information was dropped.

tojiro, 4 days ago

With no need to allow for an asynchronous permission prompt, though, the async nature of the call became an unnecessary hassle. And since Safari and Firefox haven't shipped WebGPU yet we felt this was a good opportunity to remove a small bit of developer friction. It means Chrome is going to have to go through a deprecation process, but that's worth it to us to squash a bit of historical API awkwardness.

tojiro, 4 days ago

One last thing to note: Browsers still have the option to allow users to opt-in to sharing more detailed adapter.info. For example, Chrome will expose more detailed information if you turn on "WebGPU Developer Features" in about:flags.

In any case, sorry if this causes a bit of code churn for anyone, but at the end of the day this will be a little bit easier for everyone!

tojiro, 4 days ago

@mcc Yes, exactly. And it's now synchronous because there's no reason to keep it async.

tojiro, 4 days ago

Kudos to my colleague François Beaufort for implementing the API change so quickly after the working group approved the change!

tojiro, 6 days ago

@mcc "It turns out that Yolo Smith, the trillionaire responsible for approx 5% of the global economy, is an outlier and should not have been counted. If we remove his contributions it turns out the economy has been terrible for everyone else a long time. We regret the error."

tojiro, 6 days ago

@martinlaxenaire @BenHouston3D It's going to be a breaking change long term. requestAdapterInfo() will continue working in Chrome for a while, but we'll eventually remove it when usage is low enough. Safari will likely only ship with the new .info attribute, and Firefox might do the same.

tojiro, 6 days ago

@mcc Welp, it was either gonna be that or the graphics driver.

tojiro, 6 days ago

@mcc Ah, yeah. I had a corp Linux box once that I had to exchange because 90% of the time it went to sleep it wouldn't wake up again short of a hard reboot. Good times!