objectbuffer
worktank-loader
objectbuffer | worktank-loader | |
---|---|---|
4 | 1 | |
163 | 7 | |
- | - | |
2.9 | 0.0 | |
8 days ago | about 2 years ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
objectbuffer
-
JavaScript APIs You Don’t Know About
is a great example, which I also tried to (poorly) reimplement myself.
It creates a new data structures that behave as an object for the user but is backed by SharedArrayBuffer in order to support parallel computation over it.
- [0]: https://github.com/Bnaya/objectbuffer
- Web Crypto API
-
isoworker - universal multithreading with main-thread dependencies, 6kB
There is a lot of complexity involved in representing arbitrary javascript objects inside an ArrayBuffer whilst making them thread-safe. I'd first point to a library like objectbuffer. There's also more fixed struct-like options such as Google's FlatBuffers or buffer-backed-object.
worktank-loader
-
Web Crypto API
Workers are awesome but you are right, working with them can be painful without the right tooling.
Personally I've written my own libraries for abstracting all this away and I've having a blast working with workers now, maybe check them out:
- WorkTank [1]: This abstracts away the difference between browser workers and Node worker threads, it makes it easy to make worker pools, and it can transfer simple functions to a worker at runtime too.
- WorkTank loader: This abstracts away loading asynchronous function from a worker basically, you just add ".worker" to your file name and that file and all its dependencies are transparently replaced moved to a worker, all the rest of the app (TS types for example) doesn't even notice anything happened, it just works.
You might want to check out the more popular "comlink" library too, although it didn't work for me for whatever reason and it doesn't support worker pools I believe.
[1]: https://github.com/fabiospampinato/worktank
[2]: https://github.com/fabiospampinato/worktank-loader
What are some alternatives?
proposal-atomics-wait-async - "asynchronous atomic wait" for ECMAScript
wasm-futures-executor - Executor for asynchronous task based on wasm web workers.
d2-checklist - Source for www.d2checklist.com, written in Angular and using the Bungie API
worktank - A simple isomorphic library for executing functions inside WebWorkers or Node Threads pools.
comlink - Comlink makes WebWorkers enjoyable.
rinzler - An autonomous parallel processing engine for the browser.
wireworld-player - A multithreaded web app for loading and simulating instances of the Wireworld cellular automaton
taskwork - Efficient multi-threaded task scheduler using generic re-usable WebWorkers.
fork-ts-checker-webpack-plugin - Webpack plugin that runs typescript type checker on a separate process.