[glass_of_water]

Currently, WebAssembly doesn't can't directly call any of the browser APIs; it has to call back into javascript to make any network requests, make WebGL calls, read to/write from the DOM. Projects like wasm-bindgen make it look like you're directly calling browser APIs, but it's actually calling out to a Javascript shim.

I think this project's use case is that you have a fixed query, but the dataset over which you're running that query is changing over time (getting streaming updates). The wasm part is doing the work of running the query over the dataset and updating the query results as new data streams in. So the assumption is that rendering isn't the bottleneck, but running the query is.

[XCSme]

So the dataset would be a local dataset (that gets frequently updated from the network) and the query is a local query that runs over that dataset?

I still am a bit confused about the use-case.

[XCSme]

Oh, I still I'm starting to get it.

Is it if you have a large dataset locally stored (eg. in JS memory) that receives constant updates from a server? Are there any example apps that have this architecture?

[infinite8s]

Any kind of pivoting/roll-up over streaming updates (financial trading, IOT, transportation). A lot of streaming dashboards across a number of industries are effectively just pivot tables over ticking data.