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

I just want to mention that this limitation is present also on WebHID, I just created an issue for it: https://github.com/WICG/webhid/issues/120

To be honest, the OP justification is biting us as well, we lack the support to develop performant web games with low latency.

I'm surprised and disappointed in the same time that "we" were not able to make those changes to the gamepad API for so many years:
- this issue opened in 2016
- https://github.com/w3c/gamepad/issues/19 - open since 2016
- https://github.com/w3c/gamepad/pull/152 - first issue in 2015, MR open in 2021

I think we have a chicken-egg problem here, there is not much interest from game developers, just because there are no proper tools to develop those games in browser, we have to use hacks like `runAnimationFrame` for a simple thing like a button press...

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

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