stylus
async-std-hyper
stylus | async-std-hyper | |
---|---|---|
3 | 1 | |
121 | 40 | |
- | - | |
2.6 | 0.0 | |
10 months ago | over 1 year ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
stylus
-
Show /r/Rust: keepcalm (and call Clone), a simpler way to manage synchronization
I’m making use of this in a few of my projects (https://github.com/progscrape/progscrape/ and https://github.com/mmastrac/stylus/ so far) and I’m quite happy with the quality-of-life improvements. Happy to share it with the community-at-large and solicit ideas/feedback. PRs welcome!
-
Dashy – A self-hosted homepage for your homelab
This is pretty cool.
If you don't need all the bells and whistles from this (including auth!), I built a homelab status page server that's designed for someone like me that just wants to whip up an SVG in draw.io or diagrams.net and make it semi-interactive:
https://github.com/mmastrac/stylus/
I use it to keep tabs on a small fleet of equipment and get at-a-glance status for everything.
-
Tokio, the async runtime for Rust, hits 1.0
I always get a weird vibe from async-std. I respect the people working on it, but it feels like it's trying to boil the ocean.
I'd be very interested in hearing other opinions, as my Rust project [1] is currently stuck on an older version of Tokio while I wait for deps to update.
[1] https://github.com/mmastrac/stylus/
async-std-hyper
-
Tokio, the async runtime for Rust, hits 1.0
Here is an example: https://github.com/async-rs/async-std-hyper/blob/master/READ...
You do have to write a ~50 loc compat layer. However, most of the compat layer is due to the fact that tokio's `AsyncRead` and `AsyncWrite` are different from the standard futures crate, which may change in the future [0]. After that, you just have to implement `hyper::Executor` for async-std's `spawn`, and `hyper::Accept` for async-std's `TcpListener`.
Of course, it is not as generic as `Future`, but it is relatively simple. As @steveklabnik mentioned:
> There's a few points here that still need some interop work. The intention is to fix that, but it's non-trivial. We'll get there.
[0]: https://github.com/tokio-rs/tokio/issues/2716
What are some alternatives?
rio - pure rust io_uring library, built on libc, thread & async friendly, misuse resistant
reqwest - An easy and powerful Rust HTTP Client
keepcalm - Simple shared types for multi-threaded Rust programs
async-std - Async version of the Rust standard library
smol - A small and fast async runtime for Rust
warp - A super-easy, composable, web server framework for warp speeds.
ureq - A simple, safe HTTP client
DashMachine - Another web application bookmark dashboard, with fun features.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.