pasts
Minimal and simpler alternative to the futures crate. (by ardaku)
wasm-futures-executor
Executor for asynchronous task based on wasm web workers. (by wngr)
pasts | wasm-futures-executor | |
---|---|---|
6 | 3 | |
110 | 29 | |
4.5% | - | |
4.0 | 0.0 | |
11 months ago | almost 2 years ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
pasts
Posts with mentions or reviews of pasts.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-14.
-
`alternator` gives an async function access to data but gives it back on await points
This was one of the original ideas behind pasts. I wanted to share data on a single threaded executor without using RefCell, so I created the Join struct api (renamed and redesigned many times). I'm curious what you think of that approach.
-
Pasts - A No-Std Compatible Async Runtime
Pointing out that you're comparing apples to oranges. First off, that example isn't marked #[no_std], that means it will not work on no-std. It's not the same example. You need to define a panic handler, eh_personality and an allocator all of which are conviniently ignored in your linked example because it targets std instead of no-std. If you look at the actual equivalent example in pasts, it is actually not more boilerplate: https://github.com/ardaku/pasts/blob/stable/examples/timer.rs
wasm-futures-executor
Posts with mentions or reviews of wasm-futures-executor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-17.
-
How to enable Bulk Memory Operations when compiling to WebAssembly?
RUSTFLAGS='-C target-feature=+bulk-memory' should work according to the readme of https://github.com/wngr/wasm-futures-executor
-
Threading for WASM target
I recommend using it through the wasm-futures-executor crate: https://github.com/wngr/wasm-futures-executor.
-
Web Crypto API
By the way, I built something similar (?): A Rust library that mimics the API of the `futures-executor` crate, but each worker thread is a single WebWorker.
https://github.com/wngr/wasm-futures-executor
What are some alternatives?
When comparing pasts and wasm-futures-executor you can also consider the following projects:
tarpc - An RPC framework for Rust with a focus on ease of use.
wireworld-player - A multithreaded web app for loading and simulating instances of the Wireworld cellular automaton
ghost-collections - Safe collections written in stable Rust, based on GhostCell and StaticRc.
yew - Rust / Wasm framework for creating reliable and efficient web applications
async-graphql - A GraphQL server library implemented in Rust
worktank - A simple isomorphic library for executing functions inside WebWorkers or Node Threads pools.