3 ms·
What’s the story with threading on the web these days? My impression was that the browsers have purposely and permanently handicapped some things necessary for
by et1337 3y ago
What’s the story with threading on the web these days? My impression was that the browsers have purposely and permanently handicapped some things necessary for performance in order to prevent things like rowhammer and speculative execution exploits. But I haven’t paid super close attention.
- seanisom 3y agoIt works well now! You use a SharedArrayBuffer to communicate between Web Workers. Was indeed a dark couple of years where the meltdown stuff disabled that, but there are now specific cross-origin headers that are used to isolate the SharedArrayBuffer from outside access.
- deleted 3y ago[deleted]
- dekhn 3y agoClassic inner platform effect. WASM has taken 7 years ago to get where desktop C++ was 20 years ago. Or rather, within approximate psuedo-spitting-distance to desktop.
- pjmlp 3y agoThen add the distance between 3D Web APIs and desktop 3D API and we're gold. Also add WASM versus MSIL into the mix regarding runtime capabilities.