reax-v2 VS Allusion

Since then I've been slowly working on implementing those features inside https://gitlab.com/samsartor/reax-v2. But grad school keeps me busy enough that I don't honestly know if it will ever be done. If anyone else is working on that sort of system, I'd love to trade notes!

Allusion? https://github.com/allusion-app/Allusion

You can only block a web worker thread; blocking in the main thread is not allowed by browser vendors. If you want to synchronize two web workers, you can use the std primitives like Mutex and compile with atomics. If you want to synchronize the main thread and a web worker, you need to build this yourself. I have implemented this in one of my code bases (https://github.com/allusion-app/Allusion/blob/master/wasm/masonry/src/sync.rs) but the code is GPL licensed. Note this particular code only works in browsers that support Atomics.waitAsync. An alternative is to wrap a worker.onmessage callback in a Promise and await that. Also statics are used because I don't want the overhead of calling receive from JavaScript back to Rust in the web worker, not that they are required.

One idea that could work out is to move state management to a web worker and state changes are just messages between the main thread and web worker (JS example with Redux + React + Comlink. The Redux and Comlink would be reimplemented in Rust (requires atomics, WASM intrinsics and however Redux works). However, using atomics is not so nice. Atomic.waitAsync has so far been only stabilized in Chrome last time I used it and the Rust std library has no equivalent, so you still have to call that from Rust. I've implemented something similar to a channel/spinlock but with statics (github source).

The final implementation: Masonry algorithm in Rust, Webworker, Masonry renderer which makes use of the Virtualized renderer