1 hour agoCreated a post • 24 points @belter
Deno 1.12 supports wasm threads https://deno.com/blog/v1.12#atomics-and-sharedarraybuffer-sh...Reply
The bummer with WASM threads is the COOP/COEP headers requirement once it dawns on you that this only works if you have control over the web server configuration (to set the required response headers).
This means WASM threads can't be used with popular hosting solutions like Github Pages, which in turn means that for library authors like me the feature is nearly useless because it splits the audience into people who have control over their web servers, and those who don't, which in turn means maintaining two code paths, one with and one without threading support. And even if you theoretically have control over the web server configuration it's still more hassle because the people who write the code are usually not the same people who configure the web servers. So instead of just dumping a couple of WASM files to IT you also need to find and ask the right people to tweak the web server configuration just for your use case.
Sometimes I don't understand what's going on in the heads of the people thinking this stuff up :/Reply
WebAssembly "threads" depend on SharedArrayBuffer, which is not available on Safari. Whatever your opinion of Apple or web feature adoption in Safari, this definitely puts a damper on things if you need to support mobile browsers.Reply
Unpopular opinion: We would've been better off keeping web plugins and isolating those in a "click to play"-container rather than turning the web browser into an operating system.Reply