This looks heavily geared towards graphics. I’m interested in the compute capabilities of WebGPU to build an in-browser simulator (e.g. physics/quantum). Anyone know of any good resources for that? (Samples, best practices, etc.)
WebGPU Fundamentals
101–110 of 211 posts
Re: WebGPU Fundamentals
#102Question for discussion: when have we reached the point where the Browser Feature-creep is too much and we say "okay, a browser probably doesn't need this"? Because after seeing WebUSB and WebGPU I think my personal limit has been reached.
WebGPU in browser isn't really interesting to me. But I do like WebGPU in native applications, as we are yet again in scenario where Windows prefers DX, OSX their own Metal and Vulkan is yet again mostly linux only player, and popular WebGPU implementations have backends to all of these (+ more).
Re: WebGPU Fundamentals
#103Earlier quoted context omitted.
Free yourself from the notion that a web browser purely browses The Web. It's nowadays also a cross-platform insta-deployment GUI application runtime environment with mostly bad native OS integration and performance characteristics (both ~improving, there's even native filesystem access now). In any case it's Good Enough (C), so it sticks.
> Free yourself from the notion that a web browser purely browses The Web. Free yourself from the notion that a web browser should do anything more than browsing the web. native applications have existed for decades, no reason to bloat the scope of a browser.
[deleted]
Re: WebGPU Fundamentals
#104Earlier quoted context omitted.
The browser is basically an OS ontop of an OS ontop of. .. turtles all the way down The OS runs on hardware, what do you think is below the OS you're running?
The OS runs on hardware, what do you think is below the OS you're running? Even excluding VMs, there are a lot of OSes running in a modern computer. Some chips have their own. BIOSes and Secure Enclave, networking chips, and probably a dozen more.
Try to understand the context of more than one comment at a time if you can. This person said "it's turtles all the way down" because there are two layers, the browser and the OS, which is ridiculous.
Re: WebGPU Fundamentals
#105Earlier quoted context omitted.
Browsers are just “standardised” OS at this point. Really, what is the difference? It seems to me that people basically wants a 1 to 1 mapping between every OS feature to browsers. I wouldn’t be surprised if this standard will fall apart in the next decade once Chrome runs everything. That is to say Chrome is the standard. I am already seeing websites drop support for Firefox and won’t even load using it.
> I am already seeing websites drop support for Firefox Examples?
I'm not sure if these are examples of dropped support, but I run into issues on websites that prevent me from doing something I really need to do:
- I could not unsubscribe from amazon prime yesterday using firefox. The page where you select the option was not rendering correctly. It was white for half the page vertically and the link/button I need to press was absent.
- about 6 months ago I could not sign into apple id on apples site on firefox. (or something like this, I forget exactly what I was trying to do).
- about 6 months ago I could not sign into nintendo's site to cancel a subscription.
So it's not super frequent, but every few months there are important things I can't do in firefox.
Re: WebGPU Fundamentals
#106Earlier quoted context omitted.
Because it's really cool to try out experimental instruments other poeple have made by simply opening a webpage, without having to execute untrusted native code that could have bad consequences.
AKA laziness. yes, lets please bloat of the scope of browsers until they are no longer recognizable, so that you dont have to install some software.
You oversaw the untrusted part, this is the only reason I prefer web over native really. If there was a way to run native apps with that level of isolation, I would prefer native.
Re: WebGPU Fundamentals
#107Question for discussion: when have we reached the point where the Browser Feature-creep is too much and we say "okay, a browser probably doesn't need this"? Because after seeing WebUSB and WebGPU I think my personal limit has been reached.
I think one of the main drivers of new browser features is ChromeOS. Manufacturers are selling a lot of Chromebooks, especially to schools, and because ChromeOS is primarily a conduit for running Chrome, the best way to add features to Chromebooks is by adding to the browser. From Google's point of view, anything ChromeOS needs is a candidate for a new browser feature.
Re: WebGPU Fundamentals
#108Question for discussion: when have we reached the point where the Browser Feature-creep is too much and we say "okay, a browser probably doesn't need this"? Because after seeing WebUSB and WebGPU I think my personal limit has been reached.
[deleted]
Re: WebGPU Fundamentals
#109Question for discussion: when have we reached the point where the Browser Feature-creep is too much and we say "okay, a browser probably doesn't need this"? Because after seeing WebUSB and WebGPU I think my personal limit has been reached.
In the age of app stores and notarized binaries, anything that makes the browser non-trivially more competitive with native apps is defensible.
Re: WebGPU Fundamentals
#110Highly unavailable still, but it seems to be non-experimental in chrome 113-115, as of writing this https://caniuse.com/?search=webgpu
Support should land in stable in 11 days