pollster
mustang
| pollster | mustang | |
|---|---|---|
| 3 | 20 | |
| 443 | 792 | |
| - | - | |
| 3.6 | 7.5 | |
| 6 months ago | 14 days ago | |
| Rust | Rust | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
pollster
-
Rust criticism from a Rustacean
Other than that, I'm using async mostly not in a web-based environment, unlike your assumption that the "so-called web-devs" only want to use it. It's also quite flexible, you want it blocking? Start a blocking executor. You don't want tokio for that? Use a minimal executor like https://github.com/zesterer/pollster for that...
-
Fellow Rust enthusiasts: What "sucks" about Rust?
Check out https://github.com/zesterer/pollster. This can be the solution to the async problem you described
-
Tachyonix: a very fast MPSC async bounded channel
Pollster: https://github.com/zesterer/pollster
mustang
-
OpenBSD 7.5 Released
It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.
Found this as well: https://github.com/sunfishcode/mustang
Some discussion here: https://github.com/bytecodealliance/rustix/issues/76
- Mustang
-
Rust criticism from a Rustacean
On Linux there has been some attempts to get exactly this solutions, most notibly https://github.com/sunfishcode/mustang but the topic did not seem to fetch a prominent position on the supported feature list.
-
Microsoft rewriting core Windows libraries in Rust
For Linux, Mustang already exists because Linux has a stable syscall API
- Mustang: Rust target with std and no linking to a Libc
-
The Rust Implementation Of GNU Coreutils Is Becoming Remarkably Robust
Why bother with a libc at all, when you can skip it entirely on Linux!
-
Why so few, if any, pure Rust apps?
Mustang is a project which is able to run some non-trivial programs written in Rust, such as ripgrep, without using any libc, on Linux.
-
Can rust be entirely written in rust and drop C usage in its code base ?
Mustang is one way to take care of the tiny amount of "C" that runs before main().
-
How do I use Zig as Rust's Standard C Library?
This is more a Rust question than a Zig question. In Rust, the choice of a specific libc (or to not use a libc) is part of the "target", for example many hardware platforms have gnu/musl/none targets. See also relibc or mustang for pure-rust alternatives. Each libc alternative require some work to integrate into Rust.
-
memmapix: A pure Rust library for cross-platform memory mapped IO, which replace libc with rustix.
There's a separate project for that, called Mustang. It's built on top of rustix and provides all those things. It's not super mature yet, but it is able to run ripgrep by itself: https://github.com/sunfishcode/mustang
What are some alternatives?
tachyonix - An asynchronous, multi-producer, single-consumer (MPSC) bounded channel that operates at tachyonic speeds
ziglibc
getrandom - A small cross-platform library for retrieving random data from (operating) system source
relibc - Mirror of https://gitlab.redox-os.org/redox-os/relibc
rust-delegate - Rust method delegation with less boilerplate
liblinux - Linux system calls.
dislike-in-rust - A list of the few things I don't like about rust
rustix - Safe Rust bindings to POSIX-ish APIs
SHLL - An experiment of high level code optimization
jython3 - A sandboxed attempt at v3 (not maintained)
rust-orphan-rules - An unofficial, experimental place for documenting and gathering feedback on the design problems around Rust's orphan rules
libc - Raw bindings to platform APIs for Rust