zlacker

But the chance of a web page actually needing that functionality to render at all is rare for hopefully-obvious reasons. The status quo is that progressive enhancement is dead: a few-year old copy of Safari can now simply not browse much of the web anymore because it is missing some corner case of CSS or web components or whatever: I often am stuck at loading spinners or are simply thrown into a blank page... the best case is a client-side rendered 500 error on many pages.

It was critical for the web to be easy to implement the core of for a small team or even a single concerted god-tier developer--imagine Fabrice Ballard--and the current spec has failed so hard at this that even tech megacorps have thrown in the towel. People get upset about WebUSB... but that's not the API surface that is causing us issues. If I had to single-handedly implement all of canvas/WebGL/WebGPU and JavaScript/WebAssembly I could pull it off (noting I used to be a video game engine developer).

>>saurik+(OP)
> But the chance of a web page actually needing that functionality to render at all is rare for hopefully-obvious reasons.

The chance of a page using something has no bearing on how dificault something is to implement.

> People get upset about WebUSB... but that's not the API surface that is causing us issues.

It's one of the hundreds of APIs, and yes, it causes issues, too. Because it also needs to be implemented, and it also adds to the complexity of the web browser.

>>troupo+Q5
No: it doesn't need to be implemented unless you actually want to do something with USB. Random websites aren't not working because you don't support USB. My iPhone doesn't support WebUSB even if I updated its firmware.

>>saurik+Zv
> No: it doesn't need to be implemented unless you actually want to do something with USB

Tell it to angry devs even here who lambast Safari and Firefox for not implementing Chrome's hardware APIs