- From: 7ombie <notifications@github.com>
- Date: Wed, 14 Dec 2022 18:05:46 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 15 December 2022 02:05:58 UTC
@marcoscaceres - So long as nobody couples gamepads to the DOM (which would be crazy), this issue (gamepads in workers) is essentially API-agnostic. I'm not arguing for any particular model, API or architectural decisions, only that gamepads need to be available in workers. The designers of every other relevant API accept the need for reliably handling user input with low latency, and all support workers or intend to. This general agreement is highly unlikely to change. IIUC, the WebHID API does everything that the Gamepad API does (albeit at a lower level), without the limitations. If that's correct, there's a danger of the Gamepad API becoming redundant, as library authors implement more powerful gamepad APIs on top of WebHID. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/37#issuecomment-1352462341 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/37/1352462341@github.com>
Received on Thursday, 15 December 2022 02:05:58 UTC