Earlier quoted context omitted.
> Just because you played Quake doesn't mean the web is good for "vast majority of apps" It means that at least 15 years ago it was more than powerful enough for all of the 2D Candy Crush style games which make up the overwhelming majority of mobile gaming apps. > The web can barely display simple text and images without jank because that is inherent limitation of the DOM that you cannot escape I've seen you repeat t…
One thing I can quantify directly: in Zoom's native Windows app I can reply to a question and share my screen essentially instantly. That is to say I can do like "you can see here" and I've shared my screen before I've finished speaking, in the Google Meet PWA I have to say "here let me show you..." and pause while I wait for the screen share UI to load, I find the button to share the correct screen, and go. I don't…
> but also display, audio input/output, even global keyboard shortcut handling.
I personally have never had a display or audio hiccup that I could attribute to a browser limitation. I don't even own a device with a display powerful enough to max out Youtube.com's 8K video resolution limit. I'm not sure why you've had issues with keyboard shortcuts. Keyboard events are well established and widely supported [3].
[1] https://news.ycombinator.com/item?id=20387298
[2] https://hn.algolia.com/?q=zoom+vulnerability
[3] https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEve...