Ian Kettlewell

I spent the last few hours and wrote some very sloppy code that shows a few key areas Bevy needs to change to get Wasm multithreading support: https://github.com/kettle11/bevy/commit/c8c2eb51a872f18ede40bbef7055d9b45b29acb6 The code...

With https://github.com/bevyengine/bevy/pull/12205 a first step towards getting Bevy multithreaded on web has been merged. Now it is possible to _build_ a Bevy project with multithreading enabled, even if Bevy internals...

https://github.com/smol-rs/parking/issues/20 actually already works the way it describes. Rust's std sync primitives use Wasm's atomic.wait when compiled with the `atomics` flag. So `parking` will work correctly on a worker thread...

Coming back to this. I no longer think that it will be necessary (at least for now) to involve any sort of 'busy loop' hack. Instead Rust / Wasm programs...

This conceptually looks fine to me, but @JoJoJet have you checked that this still runs with the `atomics` flag enabled? This PR has instructions for how to build with that...

Summarizing some API info here so that it may help anyone who wants to implement this: ### MacOS `NSEvent`s have a `timestamp` property that can be used: https://developer.apple.com/documentation/appkit/nsevent/1528239-timestamp?language=objc The property...

On MacOS this appears to be a non-issue. If a key is pressed, the window loses focus, and then the key is released, then the OS still sends a keyUp...