Ian Kettlewell

@alexcrichton Audio Worklets are a way to run code on the browser's dedicated audio thread. I'm specifically interested in them as they may allow sharing high-performance / low-latency audio code...

I've been looking into this a bit more again. An approach to getting around the missing text decoder is described here: https://www.toptal.com/webassembly/webassembly-rust-tutorial-web-audio The Audio Worklet can use a polyfill (this...

This isn't exactly on topic, but perhaps useful to others trying to do similar work: I managed to cobble together some code that works with Audio Worklets, Rust, and partially...

A few years later this is still a pertinent issue. In many cases native code is designed to wait extremely briefly on the main thread and in places where that...

> I'm surprised Rust projects try to execute `wait` on the main thread, though. In Emscripten `wait` instructions are only executed by system libraries that know to do something else...

> At this point, it makes me wonder if it could be a post-link feature in wasm-ld or wasm-opt where it would rewrite all atomics.wait to such conditional busy-loop automatically...

I'm frustrated with the general consensus that allowing Atomics.wait is "impossible" and "never going to happen". Who do we have to convince? Which browser people would block that change? I...

> Allowing the main thread agent to block is non-negotiable at this moment @syg Why is it non-negotiable and who are the (non) negotiating parties? I haven't seen any recent...

To reiterate: the primary stated purpose of not allowing the main thread to use `Atomics.wait` is to prevent a deadlock when a worker inadvertently waits on the main thread while...

One potential approach is to store a sparse-set of associated `Archetype`s per component. Then finding matching `Archetype`s for a query becomes the following steps: * Find the component in the...