I really hope they won’t remove SharedArrayBuffers. It’s the technology that allows multithreading in a web browser.
Since modern CPUs ship with 16 hardware threads and even 128 thread machines are coming up, it’d let a lot of performance remain on the table that could better be used to improve performance.
Having the option at least would be nice. I know the benefits of using sharedarraybuffers but right now there are a ton of websites that don’t support it. Maybe in a year or two it could be standard.
I can’t speak for the devs, but my feeling is that it would be a lot of work to maintain two systems in parallel, one multithreaded and one singlethreaded, especially for a niche platform.
Bevy does it this way (doesn’t support multithreading at all on the web), but that engine is much leaner.
I really hope they won’t remove SharedArrayBuffers. It’s the technology that allows multithreading in a web browser.
Since modern CPUs ship with 16 hardware threads and even 128 thread machines are coming up, it’d let a lot of performance remain on the table that could better be used to improve performance.
Having the option at least would be nice. I know the benefits of using sharedarraybuffers but right now there are a ton of websites that don’t support it. Maybe in a year or two it could be standard.
I can’t speak for the devs, but my feeling is that it would be a lot of work to maintain two systems in parallel, one multithreaded and one singlethreaded, especially for a niche platform.
Bevy does it this way (doesn’t support multithreading at all on the web), but that engine is much leaner.