back on my bullshit! @bomb.sh/runtime poc
syntax is rough, but i'm thrilled the concept works
jsx writes directly to a SharedArrayBuffer
rust reads from it, taffy does layout, crossterm renders
preact/signals-core handles reactivity
syntax is rough, but i'm thrilled the concept works
jsx writes directly to a SharedArrayBuffer
rust reads from it, taffy does layout, crossterm renders
preact/signals-core handles reactivity
March 21, 2026 at 4:12 AM
back on my bullshit! @bomb.sh/runtime poc
syntax is rough, but i'm thrilled the concept works
jsx writes directly to a SharedArrayBuffer
rust reads from it, taffy does layout, crossterm renders
preact/signals-core handles reactivity
syntax is rough, but i'm thrilled the concept works
jsx writes directly to a SharedArrayBuffer
rust reads from it, taffy does layout, crossterm renders
preact/signals-core handles reactivity
Need cross-thread synchronization without freezing the main thread? 🥶
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
January 5, 2026 at 5:23 PM
Need cross-thread synchronization without freezing the main thread? 🥶
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Need cross-thread synchronization without freezing the main thread? 🥶
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
January 14, 2026 at 1:00 PM
Need cross-thread synchronization without freezing the main thread? 🥶
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Need cross-thread synchronization without freezing the main thread? 🥶
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
November 28, 2025 at 4:00 AM
Need cross-thread synchronization without freezing the main thread? 🥶
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Atomics.waitAsync() returns immediately and resolves when another thread calls Atomics.notify().
Perfect for coordinating workers with SharedArrayBuffer.
Learn more 👇
developer.mozilla.org/en-US/docs/...
Hm this feels like oversight.
Am I really supposed to be able to construct shared Wasm memory (backed by a SharedArrayBuffer) on insecure pages where normally SharedArrayBuffer is not exposed?
Am I really supposed to be able to construct shared Wasm memory (backed by a SharedArrayBuffer) on insecure pages where normally SharedArrayBuffer is not exposed?
February 24, 2025 at 2:00 PM
Hm this feels like oversight.
Am I really supposed to be able to construct shared Wasm memory (backed by a SharedArrayBuffer) on insecure pages where normally SharedArrayBuffer is not exposed?
Am I really supposed to be able to construct shared Wasm memory (backed by a SharedArrayBuffer) on insecure pages where normally SharedArrayBuffer is not exposed?
SuperSonic now exposes the scsynth node tree for fast reading from JS.
This does not require a full OSC round-trip like /g_queryTree (which is also supported for legacy use cases).
Instead it’s automatically written to the SharedArrayBuffer so visualisers can read it at 60fps without issue.
This does not require a full OSC round-trip like /g_queryTree (which is also supported for legacy use cases).
Instead it’s automatically written to the SharedArrayBuffer so visualisers can read it at 60fps without issue.
December 11, 2025 at 1:43 PM
SuperSonic now exposes the scsynth node tree for fast reading from JS.
This does not require a full OSC round-trip like /g_queryTree (which is also supported for legacy use cases).
Instead it’s automatically written to the SharedArrayBuffer so visualisers can read it at 60fps without issue.
This does not require a full OSC round-trip like /g_queryTree (which is also supported for legacy use cases).
Instead it’s automatically written to the SharedArrayBuffer so visualisers can read it at 60fps without issue.
GitHub Pagesでも`SharedArrayBuffer`を使いたい | Memory ice cubes
https://leaysgur.github.io/posts/2025/05/26/171223/
https://leaysgur.github.io/posts/2025/05/26/171223/
GitHub Pagesでも`SharedArrayBuffer`を使いたい | Memory ice cubes
leaysgur.github.io
May 26, 2025 at 9:35 PM
GitHub Pagesでも`SharedArrayBuffer`を使いたい | Memory ice cubes
https://leaysgur.github.io/posts/2025/05/26/171223/
https://leaysgur.github.io/posts/2025/05/26/171223/
Has anyone created a friendly parallelism framework for JS that leverages Web Worker, `SharedArrayBuffer` and `Atomics`?
May 30, 2023 at 10:22 AM
Has anyone created a friendly parallelism framework for JS that leverages Web Worker, `SharedArrayBuffer` and `Atomics`?
you can just store everything in a sharedarraybuffer it's legal and the cops can't stop you
January 29, 2026 at 4:48 PM
you can just store everything in a sharedarraybuffer it's legal and the cops can't stop you
I went back to work two weeks ago, and since then I have not even looked at my ongoing work on Nova #JavaScript engine's SharedArrayBuffer usage as I have simply not had the time.
Feels weird coming back to it. Feels like a total brain reset.
Feels weird coming back to it. Feels like a total brain reset.
October 18, 2025 at 6:11 AM
I went back to work two weeks ago, and since then I have not even looked at my ongoing work on Nova #JavaScript engine's SharedArrayBuffer usage as I have simply not had the time.
Feels weird coming back to it. Feels like a total brain reset.
Feels weird coming back to it. Feels like a total brain reset.
Jarred Sumner experiments with multi-threaded JavaScript 🧪
Filip Pizlo's "wild thought experiment" from 2017 is brought to life 🔥
Unlike existing approaches (workers, SharedArrayBuffer) this shares the JS heap. It means threads directly access the same JS objects.
github.com/oven-sh/WebK...
Filip Pizlo's "wild thought experiment" from 2017 is brought to life 🔥
Unlike existing approaches (workers, SharedArrayBuffer) this shares the JS heap. It means threads directly access the same JS objects.
github.com/oven-sh/WebK...
June 10, 2026 at 7:37 AM
Jarred Sumner experiments with multi-threaded JavaScript 🧪
Filip Pizlo's "wild thought experiment" from 2017 is brought to life 🔥
Unlike existing approaches (workers, SharedArrayBuffer) this shares the JS heap. It means threads directly access the same JS objects.
github.com/oven-sh/WebK...
Filip Pizlo's "wild thought experiment" from 2017 is brought to life 🔥
Unlike existing approaches (workers, SharedArrayBuffer) this shares the JS heap. It means threads directly access the same JS objects.
github.com/oven-sh/WebK...
Sadly when using SharedArrayBuffer support option for web games, this doesn't work.
July 14, 2025 at 5:20 PM
Sadly when using SharedArrayBuffer support option for web games, this doesn't work.
Далі багато джаваскріпт/webgl сленга
TIL: double buffering на запис у Worker'ах і читання з головного треду, синхронізація через Atomics, один SharedArrayBuffer на всі воркери, і gl.bufferSubData - може бути сильно повільніше, ніж тупо трансферити масиви в postMessage, склеювати їх і gl.bufferData🤯
TIL: double buffering на запис у Worker'ах і читання з головного треду, синхронізація через Atomics, один SharedArrayBuffer на всі воркери, і gl.bufferSubData - може бути сильно повільніше, ніж тупо трансферити масиви в postMessage, склеювати їх і gl.bufferData🤯
March 3, 2025 at 1:54 PM
Далі багато джаваскріпт/webgl сленга
TIL: double buffering на запис у Worker'ах і читання з головного треду, синхронізація через Atomics, один SharedArrayBuffer на всі воркери, і gl.bufferSubData - може бути сильно повільніше, ніж тупо трансферити масиви в postMessage, склеювати їх і gl.bufferData🤯
TIL: double buffering на запис у Worker'ах і читання з головного треду, синхронізація через Atomics, один SharedArrayBuffer на всі воркери, і gl.bufferSubData - може бути сильно повільніше, ніж тупо трансферити масиви в postMessage, склеювати їх і gl.bufferData🤯
Настя Котова продолжает круто рассказывать про особенности работы с памятью в JS.
В новом после она рассказала про SharedArrayBuffer.
t.me/startpoint_d...
В новом после она рассказала про SharedArrayBuffer.
t.me/startpoint_d...
Настя Котова // Frontend & Node.js
Продолжаю серию. В этот раз — про SharedArrayBuffer и историю с отключением во всех браузерах. SharedArrayBuffer — почти то же самое, что ArrayBuffer, но с одним принципиальным отличием: его можно передать в несколько Web Workers одновременно, и все они будут работать с одной и той же памятью. const sab = new SharedArrayBuffer(256); worker.postMessage(sab); // worker получает доступ к той же памяти С обычным ArrayBuffer при передаче через postMessage происходит transfer — оригинал становится недоступным, а получатель получает владение. Это сделано намеренно: два потока не должны одновременно писать в одну память без синхронизации. SharedArrayBuffer снимает это ограничение — но тогда синхронизацию нужно делать самостоятельно. Для этого существует объект Atomics. Он предоставляет атомарные операции — гарантированно неделимые чтение-запись: const sab = new SharedArrayBuffer(4); const view = new Int32Array(sab); // В воркере 1: Atomics.add(view, 0, 1); // атомарный инкремент // В воркере 2: Atomics.load(view…
t.me
April 10, 2026 at 10:58 AM
Настя Котова продолжает круто рассказывать про особенности работы с памятью в JS.
В новом после она рассказала про SharedArrayBuffer.
t.me/startpoint_d...
В новом после она рассказала про SharedArrayBuffer.
t.me/startpoint_d...
Yes I know about SharedArrayBuffer, however that needs fancy headers and causes massive memory leaks on Safari.
January 23, 2025 at 3:40 PM
Yes I know about SharedArrayBuffer, however that needs fancy headers and causes massive memory leaks on Safari.
見てる: "GitHub Pagesでも`SharedArrayBuffer`を使いたい | Memory ice cubes" https://leaysgur.github.io/posts/2025/05/26/171223/
May 26, 2025 at 12:22 PM
見てる: "GitHub Pagesでも`SharedArrayBuffer`を使いたい | Memory ice cubes" https://leaysgur.github.io/posts/2025/05/26/171223/
As of v0.21.6 SuperSonic now works directly from CDN - no special headers are needed - which makes deployment *dramatically* easier.
There's now two modes:
1. The original SAB (SharedArrayBuffer) mode which is *marginally* faster and less jittery - but requires stricter security
2. SAB-free mode.
There's now two modes:
1. The original SAB (SharedArrayBuffer) mode which is *marginally* faster and less jittery - but requires stricter security
2. SAB-free mode.
December 27, 2025 at 10:30 AM
As of v0.21.6 SuperSonic now works directly from CDN - no special headers are needed - which makes deployment *dramatically* easier.
There's now two modes:
1. The original SAB (SharedArrayBuffer) mode which is *marginally* faster and less jittery - but requires stricter security
2. SAB-free mode.
There's now two modes:
1. The original SAB (SharedArrayBuffer) mode which is *marginally* faster and less jittery - but requires stricter security
2. SAB-free mode.
another day in less known Web APIs, another issue in
@firefox
bugzilla.mozilla.org/show_bug.cgi...
watch out: if you use MessageChannel to pass SharedArrayBuffer and you wait synchronously (also because in FF waitAsync is still not there) your program will be stuck forever 😞
@firefox
bugzilla.mozilla.org/show_bug.cgi...
watch out: if you use MessageChannel to pass SharedArrayBuffer and you wait synchronously (also because in FF waitAsync is still not there) your program will be stuck forever 😞
1956778 - MessageChannel SharedArrayBuffer
UNCONFIRMED (nobody) in Firefox - Untriaged. Last updated 2025-03-27.
bugzilla.mozilla.org
March 27, 2025 at 11:55 AM
another day in less known Web APIs, another issue in
@firefox
bugzilla.mozilla.org/show_bug.cgi...
watch out: if you use MessageChannel to pass SharedArrayBuffer and you wait synchronously (also because in FF waitAsync is still not there) your program will be stuck forever 😞
@firefox
bugzilla.mozilla.org/show_bug.cgi...
watch out: if you use MessageChannel to pass SharedArrayBuffer and you wait synchronously (also because in FF waitAsync is still not there) your program will be stuck forever 😞
昨日Gif画像を投稿に出す処理の実装をしてたんだけど、TypeScript5.xからSharedArrayBufferが含まれているArrayBufferLike型がBlobデータに受け付けなくなってエラーが出たんよね。SharedArrayBufferはスレッド間で値が参照できるものなんで、セキュリティ上のリスク抱えているし、当然対策されるべきものですね。
January 22, 2026 at 4:26 AM
昨日Gif画像を投稿に出す処理の実装をしてたんだけど、TypeScript5.xからSharedArrayBufferが含まれているArrayBufferLike型がBlobデータに受け付けなくなってエラーが出たんよね。SharedArrayBufferはスレッド間で値が参照できるものなんで、セキュリティ上のリスク抱えているし、当然対策されるべきものですね。
Lock-free ring buffers, shared task queues, and multi-worker synchronization patterns that eliminate postMessage serialization overhead in production JavaScript applications.
#JavaScript #WebDev #Programming #TypeScript #Coding
#JavaScript #WebDev #Programming #TypeScript #Coding
JavaScript Atomics and SharedArrayBuffer in 2026: Practical Patterns for Cross-Worker State
Lock-free ring buffers, shared task queues, and multi-worker synchronization patterns that eliminate postMessage serialization overhead in production JavaScript applications.
jsmanifest.com
July 13, 2026 at 7:19 PM
Lock-free ring buffers, shared task queues, and multi-worker synchronization patterns that eliminate postMessage serialization overhead in production JavaScript applications.
#JavaScript #WebDev #Programming #TypeScript #Coding
#JavaScript #WebDev #Programming #TypeScript #Coding
i feel compelled to mention that this required CORS header junk for SharedArrayBuffer, a specific version of rust toolchain, and recompiling the standard library with atomic support. but now the web trembles
January 31, 2026 at 9:11 PM
i feel compelled to mention that this required CORS header junk for SharedArrayBuffer, a specific version of rust toolchain, and recompiling the standard library with atomic support. but now the web trembles
📬 PPSSPP-Web: PSP-Emulator läuft jetzt direkt im Browser
#Gaming #RetroComputing #Angular #AntonioRicciardi #PPSSPPWeb #PSPEmulator #roothunter #SharedArrayBuffer #WebAssembly
#Gaming #RetroComputing #Angular #AntonioRicciardi #PPSSPPWeb #PSPEmulator #roothunter #SharedArrayBuffer #WebAssembly
PPSSPP-Web: PSP-Emulator läuft jetzt direkt im Browser
PPSSPP-Web bringt eine PSP-Emulation per WebAssembly direkt in die Browser Chrome, Firefox & Safari. Eine Installation ist nicht mehr nötig.
Der Artikel <a href="https://tarnkappe.info/artikel/gaming/ppsspp-web-psp-emulator-laeuft-jetzt-direkt-im-browser-329830.html">PPSSPP-Web: PSP-Emulator läuft jetzt direkt im Browser</a> erschien zuerst auf <a href="https://tarnkappe.info">TARNKAPPE.INFO</a>
sc.tarnkappe.info
June 6, 2026 at 8:57 AM