Re:Standalone WebAssembly games using I/O devices
by meheleventyone on Sunday January 19, 2020 @05:37PM
(#22094635)
In general if you are writing a game (that you expect to ship on multiple platforms) you’ll have some cross-platform layer that makes swapping out runtimes for each platform easy. Then the game is built on top of that. Could be in the same language or in another or both. For example LuaJIT has been popular. WebAssembly provides another target.
Browsers are similar in that they are like mini-sandboxed OS’s with “standardised” interfaces. So applying the idea of standardised, sandboxed interfaces to WebAssembly you end up with WASI and probably eventually extension to GPU, audio and other interfaces useful to games.
It’s actually a pretty old idea, plenty of old games were actually written to run on interpreters that were then rewritten for each platform. For example Another World which has cropped up on the front page recently takes this approach.
Re:Standalone WebAssembly games using I/O devices
by WAHa_06x36 on Sunday January 19, 2020 @04:06PM
(#22094078)
This I/O device thing seems to be a feature of one specific wasm engine that just exposes a simple framebuffer, so, it has nothing to do with anything else.
Re:Standalone WebAssembly games using I/O devices
by pfisch on Sunday January 19, 2020 @02:59PM
(#22093589)
You can compile unity to web assembly. There are several other similar engines out there that compile to wasm.
Re:Standalone WebAssembly games using I/O devices
by xyproto on Friday January 24, 2020 @03:09AM
(#22136311)
Yes, and while that is super cool and nifty, I am struggling to find the perfect use-case for this.
When people write interactive 3D graphics for the web, there's ThreeJS and WebGL.
Where does WebAssembly games using I/O devices fit in all of this?