- From: 7ombie <notifications@github.com>
- Date: Fri, 20 Sep 2024 13:02:02 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/gamepad/issues/37/2364532512@github.com>
> We actually found a way to query the gamepadAPI way more often ... @razvanphp - Nice! I'm glad you found a solution to your specific issue, but the main thread will still be too busy to respond to user input some of the time. It's the main thread. So, we cannot (generally) implement anything that depends on reliable, low-latency user input (many games, realtime audio, anything with a stylus *et cetera*). > Let's not dramatise this more than it's needed... Sorry. I didn't mean to be melodramatic. Still, that is my genuine feeling about this. I got into Swift, Metal and Apple Silicon, and began to really enjoy programming again. I only do anything on the Web now because one of my kids wants to learn coding, make some games, and share them, and they picked the Web for that. The thing is, the Web has WebGPU, and has had WebGL 2 for ages. It also has stuff like WebAssembly and audio worklets... Point being, almost every aspect of Web development can be made performant, if you're willing to work with lower-level APIs, *except* user input. There's nothing I can do about that. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/37#issuecomment-2364532512 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/37/2364532512@github.com>
Received on Friday, 20 September 2024 20:02:06 UTC