Re:Replacing JavaScript Hot Path with WebAssembly
by barrystaes on Friday February 15, 2019 @02:23AM
(#19169106)
Hmm.. the Google article stipulates:
> WebAssembly on the other hand is built entirely around raw execution speed. So if we want fast, predictable performance across browsers for code like this, WebAssembly can help.
So i wanted to see how i could use WebAssembly in a React webapps. I found this SO question sees the opposite:
> When running this [ WebAssembly] code in Chrome, I observe "pauses" that cause the app to be a bit jittery. Running the app in Firefox is a lot faster and smoother.
> WebAssembly on the other hand is built entirely around raw execution speed. So if we want fast, predictable performance across browsers for code like this, WebAssembly can help.
So i wanted to see how i could use WebAssembly in a React webapps. I found this SO question sees the opposite:
> When running this [ WebAssembly] code in Chrome, I observe "pauses" that cause the app to be a bit jittery. Running the app in Firefox is a lot faster and smoother.
https://stackoverflow.com/questions/53584607/react-app-with-...
Same code, different browser, different performance. I'd love seeing a Google Developer answering that question in depth..