Popular posts

Multithreading isn't ever really about the language, it's about the libraries. For JS, that's DOM. SharedArrayBuffer + atomics get us mutable shared memory for some applications, but that doesn't make the rest of the DOM or object model instantly threadable.

It does, however, open up threading as part of our design language. For instance, a few years back, we had a big design argument about some details of Web Audio. There was an incidental part of the design that happened to expose mutable shared memory between threads. Because JS had no way to "explain" that, it had to go. Now that we have SAB (once Spectre mitigations are in place, that is), we'll be able to address those lower-latency use-cases in a coherent way. That's pretty exciting, particularly for VR and AR which need peak performance.