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

> I don't care anymore.

Let's not dramatise this more than it's needed....

We actually found a way to query the gamepadAPI way more often than with requestAnimationFrame or setTimeout, using [this method described here](https://dbaron.org/log/20100309-faster-timeouts), just by changing `window` with the `worker` context for the "ping-pong".

This way, we can go lower than 4ms, to around 0.02ms, with the cost of increased CPU usage of the browser.

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

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