3 ms·
For computation, sure. But isn't the wasm/js to DOM boundary always going to be a bottleneck? Maybe I'm being too negative and a faster browser API will be dev
by kevinmgranger 4y ago
For computation, sure. But isn't the wasm/js to DOM boundary always going to be a bottleneck?
Maybe I'm being too negative and a faster browser API will be developed.
- toyg 4y agobottleneck compared to what, native desktop drawing? Obviously, but that's not really an option anymore. Compared to JS performance over the same tasks - that's where WASM improvements should deliver. It doesn't have to be as fast as JS, just fast enough to become an acceptable alternative for the average case.