1. The elephant in the room, Apple, is highly non compliant with web standards (iOS Safari lacks js web workers, webgl 2, WebRTC data channel, and many many others)
2. The roadmap of webassembly is merely the start of glaring unsolved problems
3. GPU compute will play an increasingly important role in the future, given the advent of AI, complex cryptography, video, image,... The web and browser have outdated and insufficient support for the same
4. Access to sensors and peripherals is abysmal. WebUsb is a step in the right direction, but much needs to happen there
What is missing is shared workers support (and producing output from console.log in web workers). Of the two, shared workers would be a particularly useful feature, as it would in theory enable different browser tabs to utilize a shared, potentially resource hungry script, as per the Mozilla description at https://developer.mozilla.org/en-US/docs/Web/API/SharedWorke...
The devs at Apple claims that this use case is not relevant and/or better served by Service Workers (which is even less supported). Not sure I understand their reasoning. https://bugs.webkit.org/show_bug.cgi?id=116359
I started to find the compliance tables on MDN outdated. I am not sure how they are being updated but my guess is that it is manual and needs to be revisited.
1. The elephant in the room, Apple, is highly non compliant with web standards (iOS Safari lacks js web workers, webgl 2, WebRTC data channel, and many many others)
2. The roadmap of webassembly is merely the start of glaring unsolved problems
3. GPU compute will play an increasingly important role in the future, given the advent of AI, complex cryptography, video, image,... The web and browser have outdated and insufficient support for the same
4. Access to sensors and peripherals is abysmal. WebUsb is a step in the right direction, but much needs to happen there