3 ms·

Thanks. Yes, that makes sense. The web version of the game is powered by WebAssembly and renders to a canvas. The game is only able to utilize one CPU core whe

Thanks. Yes, that makes sense. The web version of the game is powered by WebAssembly and renders to a canvas. The game is only able to utilize one CPU core when running in the browser, maxing that core out probably set off your fans.

NooneAtAll3 2y ago
...isn't webassembly supposed to be more efficient?
- tslocum 2y ago
  The reduced performance is a Go problem rather than a WebAssembly problem. See this issue for more info: https://github.com/golang/go/issues/28631 https://github.com/golang/go/issues/28631
deleted 2y ago
[deleted]