4 ms·
Honest question: does webassembly do anything about speeding up the Dom API? For example low-latency text input is non-existent in any browser engine today (sho
by shrimpx 8y ago
Honest question: does webassembly do anything about speeding up the Dom API? For example low-latency text input is non-existent in any browser engine today (short of rendering text using webgl). Does wasm do anything about this?
- s_y_n_t_a_x 8y agoCurrently there's no way to interact with the Dom API from WASM directly, you have to interop with JS functions, so if anything, it's slower than JavaScript due to the interop bottleneck.
- andai 8y agoAre you talking about textarea and input being high latency?
- shrimpx 8y agoYeah textarea and also keyboard events. I was wondering because the comment to which I was replying implies that wasm could make the browser the defacto framework for cross platform code. But I don't think this will be the case if the native APIs continue to be low performance.
- kevingadd 8y agoIt makes it worse. Eventually it might make it slightly better via strong typing and reduced GC. Latency is largely a deficiency in the design of browsers (multiprocess rasterization, gc blocking the event loop, etc)
- fmakunbound 8y agoStuff is changing all the time implementation wise, but the architecture of WASM will enable faster-than-JavaScript access to the DOM https://hacks.mozilla.org/2018/04/javascript-to-rust-and-back-again-a-wasm-bindgen-tale/ https://hacks.mozilla.org/2018/04/javascript-to-rust-and-bac... Also, I think this might be the tipping point where web UI applications begin to be built in WASM-targeting-languages rather than JavaScript