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

I sent a message to the W3C mailing list about nine months ago explaining that the Web has a general problem with low latency user input, which makes the Web a poor choice for a number of applications, especially games and realtime audio. It didn't really go anywhere.

The keyboard and mouse are in the worse position, as they don't even have a spec that *could* support workers (they're part of the DOM API, which is married to the main thread). The Gamepad API *could* do something for controllers (WebUSB is available in workers, and WebMIDI have agreed to support workers - eventually), but without meaning any disrespect, the spec process for the Gamepad API has always been dysfunctional (the other specs are just painfully slow).

Frankly, I gave up on the Web a while back. It doesn't have the features you need, you can't implement them yourself, nobody else is going to implement them in any foreseeable future - they won't even add them to the spec - and the community doesn't care. They install so many layers of crap on top of the browser, it makes no difference how the browser actually works. If you call yourself a "React dev"...

I don't care anymore.

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

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