For ticking data being pushed into bespoke pivots, running this on the backend and, say, pushing renders to the frontend isn't generally better. You're not like

For ticking data being pushed into bespoke pivots, running this on the backend and, say, pushing renders to the frontend isn't generally better. You're not likely to be sharing much of the grunt. Also, latency will be an issue so you need to be pretty careful with GC runtimes that aren't optimised for latency. > What is the performance of doing it this way vs. without WASM and workers? @dman says in another thread that the original was in Python and this was 10x faster. If this met their performance goals, it does the job. It may be possible that another way is better, for some definition of better, but who cares if it works as required? > Until we see numbers, this smells like a recruiting play. It's presumably OK not to use it if you don't want to. And what if they think this may help recruiting? Seems like a reasonable trade to me.