Audjust - Snappy UIs With WebAssembly and Web Workers
Published: 2023-08-07 Our web app allows users can change the length of a song or find loops present in it for infinite listening, remixing, or for their next next video edit or performance. After uploading a song, there is an initial server-side analysis step after which the audio can be manipulated completely in the browser. Users can alter the desired length or mark sections of audio to prefer
Building secure web apps using Web Workers | Mercari Engineering
Security is paramount for our users, and we at mercari strive to provide a snappy and safe platform. We recently introduced an additional layer of defence by adding Web Workers to secure the access token. It now protects the users from various kinds of attacks, including token theft from Cross Site Scripting (XSS), Cross Site Request Forgery (CSRF), prototype pollution, zero-day npm package vulner
JavaScript Development: Making a Web Worker optional
In case you have a lot of JavaScript related logic running inside a main thread or a Web Worker, it makes perfect sense to move expensive logic into another worker. Workers run inside a different thread using their own CPU if possible. However, there can be use cases where in some scenarios there is a lot of JS related workload on a given thread, while in other scenarios this thread is mostly idle
GitHub - neomjs/neo: The Application Engine for the AI Era. A multi-threaded, AI-native runtime with a persistent Scene Graph, enabling AI agents to introspect and mutate the living application structure in real-time.
🚀 True Multithreading Meets Context Engineering — Build Desktop-Class UIs with an AI Co-Developer. ⚡ The Mental Model: Neo.mjs is a multi-threaded application runtime where UI components are persistent objects—not ephemeral render results. This architectural shift enables desktop-class performance, multi-window orchestration, and AI-driven runtime mutation that traditional frameworks cannot achie
David East - Simplify Web Worker code with Comlink
Workers are brilliant. A single worker can give the main thread some much needed breathing room, extending an application’s processing capacity. The application’s UI hums along whether you’re processing video, auto-tuning some audio, or generating a dank meme. But if workers are so great, why are they so under utilized? Are UI performance issues not common? That can’t be the case in a world full o
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - chrisguttandin/worker-timers: A replacement for setInterval() and setTimeout() which works in unfocused windows.
GitHub - slashd-analytics/run: Run user-provided code in a Web Worker
GitHub - Shopify/remote-dom
Multithreaded Javascript
GitHub - alesgenova/post-me: 📩 Use web Workers and other Windows through a simple Promise API
GitHub - mizchi/minlink: Minimum(> 1kb) and isomorphic worker wrapper with comlink like rpc.
GitHub - Bnaya/objectbuffer: JavaScript Object like api, backed by an arraybuffer
GitHub - developit/web-worker: Consistent Web Workers in browser and Node.
Define serialization and deserialization steps for Error by yutakahirano · Pull Request #4665 · whatwg/html
comlink/CHANGELOG.md at master · GoogleChromeLabs/comlink
GitHub - teamdomy/wasp: Web Workers Superset
WorkerDOM: Concurrency for JavaScript programming with the DOM
https://bugs.chromium.org/p/chromium/issues/detail?id=680046
GitHub - GoogleChromeLabs/comlink: Comlink makes WebWorkers enjoyable.
GitHub - kwolfy/webworker-promise: Promise based wrapper for webworkers
