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
GitHub - Shopify/remote-dom
Remote DOM lets you take a tree of DOM elements created in a sandboxed JavaScript environment, and render them to the DOM in a different JavaScript environment. This allows you to isolate potentially-untrusted code off the main thread, but still allow that code to render a controlled set of UI elements to the main page. The easiest way to use Remote DOM is to synchronize elements between a hidden
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: Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.
Neo.mjs is a professional, end-to-end AI engineering team that lives in its own open-source repository. ▶ Watch Neo.mjs — Agent Fleet Manager Where the industry runs one AI agent and gets slop, Neo.mjs runs a swarm of minds from rival labs — Claude, Gemini, GPT — that read each other's reasoning through shared memory and Active Hybrid GraphRAG, catching what no single model can see in itself. Thro
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
https://engineering.mercari.com/en/blog/entry/20220930-building-secure-apps-using-web-workers/
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
