EDIT: For the latest of GopherJS/Wasm comparison, see Wasm benchmark result
Hi all!
This article describes about my experiment of the new WebA...
For further actions, you may consider blocking this person and/or reporting abuse
Can you try replacing setTimeout in L307 of wasm_exec.js (github.com/golang/go/blob/master/m...) with requestAnimationFrame and see if that gives any boost in performance ?
Thanks, I'll try. I'm worried that this might conflict with rAF on the game side.
My worry was right: FPS is now up to 30 when the number of sprites are small (e.g. 100 or so), while FPS was 60 before the fix.
Got it. Thanks for giving it a shot.
This was really interesting to read! I also expected WebAssembly to be faster. I'm definitely going to look into GopherJS and Ebiten.