Re: [w3c/gamepad] Make gamepads accessible by web worker (#37)

I don't mean to rant, but the Web has an *Input Problem*. It is basically impossible to reliably respond to user input, of any kind, with low latency, on the Web. This has all kinds of subtle (but fundamental) implications that prevent the Web moving forwards. Low latency input is critical for a wide range of applications.

In every practical sense, the DOM API (with its DOM-based keyboard and pointer events) is inextricably tied to the main thread. Every other input API (gamepad, MIDI, USB, BlueTooth, Serial) should be available in workers (and worklets as appropriate).

Longterm, I hope (and expect) that we will also get some kind of new keyboard and pointer APIs that handle their events globally, and are available in workers. Regardless, the other input APIs (that are intrinsically global) should never be tied to the DOM or the main thread.

The Gamepad API is currently contributing to the Input Problem.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/37#issuecomment-1345733132
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/37/1345733132@github.com>