2 ms·
> This isn't exactly a massive obstacle if you've set out to build a complex game in the browser. It is an obstacle (at least a massive annoyance) for library
by flohofwoe 6y ago
> This isn't exactly a massive obstacle if you've set out to build a complex game in the browser.
It is an obstacle (at least a massive annoyance) for library authors (like this: https://github.com/floooh/sokol https://github.com/floooh/sokol). Those libraries can be used for extremely simple and small WASM snippets embedded in blog posts (like here: https://floooh.github.io/2019/01/05/wasm-embedding.html https://floooh.github.io/2019/01/05/wasm-embedding.html), or in "proper" games hosted through "proper" hosting services which allow to set the response headers.
Right now the choice is to either support WASM threading, but tell library users that the library will most likely not work on the hosting solution of their choice, or not support WASM threading and work everywhere. At least to me it's clear that "works everywhere" is better than "it's complicated", so I'll ignore WASM threading until the problem is solved somehow (either most hosting services turn on those response headers, or there's another way to enable threading without requiring control over the web server configuration).
- rewq4321 6y ago> It is an obstacle (at least a massive annoyance) for library authors Yeah that's a completely fair point. Ruffle dev makes a similar argument up-thread: https://news.ycombinator.com/item?id=27199260 https://news.ycombinator.com/item?id=27199260