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

As a counter to what I wrote above, I'd like to draw attention to what @beidson said (https://github.com/w3c/gamepad/issues/37#issuecomment-345017683):

> Handling Gamepads from workers would be like handling mouse/keyboard/touch/pointer events from workers, which is (of course) not done.

Put differently, if you had a game that supported both Gamepad and keyboard input (and/or mouse), you would still need to keep a lot of the logic on main thread. I imagine most games fall under this category, supporting multiple input modalities for control. 

So again, does it really make sense to privilege Gamepad in a worker when all other input devices only fire events on the main thread? Is a gamepad input so special as an input source (compared to mouse/keyboard/touch/pointer) that it warrants such special treatment in a worker scope? 

On reflection, that claim now seems dubious to me. However, making Gampads behave like other input sources by using an eventing model does seem to make sense. 

My feeling is that we should prioritize the eventing model - and if that proves insufficient, the come back and talk about Workers. 


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

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