async-std
Warp
Our great sponsors
async-std | Warp | |
---|---|---|
19 | 58 | |
3,836 | 18,710 | |
1.0% | 6.8% | |
5.3 | 7.6 | |
2 months ago | 25 days ago | |
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.
async-std
-
Stabilizing async fn in traits in 2023 | Inside Rust Blog
But maybe check out the discussion here https://github.com/async-rs/async-std/pull/631 or something (the blog post was linked on the end of it)
-
Anyone using io_uring?
Have a look at these: https://github.com/async-rs/async-std/tree/main/examples
-
Any plans for built-in support of Vec2/Vec3/Vec4 in Rust?
In fact, there are a lot of crates in Rust where in other programming languages, it would be included in the standard library. Examples are regex, random number generators, additional iterator methods, macros for other collections, num traits, loggers, HTTP libraries, error handling, async runtimes, serialization and deserialization, date and time, and many more.
-
18 factors powering the Rust revolution, Part 2 of 3
Two major projects (non std lib but extremely commonly used) stand out in the area of async programming: Async std and Tokio - no doubt familiar to anyone that has turned an eye towards Rust for a second too long. Async architecture in general is likely very familiar to JavaScript programmers but in Rust there are some extra considerations (like ownership of the data that is thrown into an async function). Tokio is fast becoming a heavily supported and road tested async framework, with a thread scheduling runtime "baked in" that has learned from the history of Go, Erlang, and Java thread schedulers.
-
What are the side-effects of using different runtimes in the same codebase?
Ah... https://github.com/tokio-rs/tokio and https://github.com/async-rs/async-std ?
-
Hey Rustaceans! Got an easy question? Ask here (51/2021)!
async-std: Basically a Tokio alternative with a few different design decisions.
-
Why asynchronous Rust doesn't work
Go's solution is for the scheduler to notice after a while when a goroutine has blocked execution and to shift goroutines waiting their turn to another thread. async-std pondered a similar approach with tasks, but it proved controversial and was never merged.
-
Building static Rust binaries for Linux
This indicates curl, zlib, openssl, and libnghttp2 as well as a bunch of WASM-related things are being dynamically linked into my executable. To resolve this, I looked at the build features exposed by surf and found that it selects the "curl_client" feature by default, which can be turned off and replaced with "h1-client-rustls" which uses an HTTP client backed by rustls and async-std and no dynamically linked libraries. Enabling this build feature removed all -sys dependencies from androidx-release-watcher, allowing me to build static executables of it.
-
Rust async is colored, and that’s not a big deal
And also, the actual PR never got merged.
-
Rust's async isn't f#@king colored!
Async in rust needs a runtime (aka executor) to run. You can maybe get a better description from the rust docs. As an example, Tokio attempts to provide an interface for a developer that is minimal change to the more common blocking code. So you'd end up putting #[tokio::main] above your main function to spin up the executor and most of the rest of the code is similar to a non-async version with a few sprinkles of .await, which you can see in the hello world for tokio. In contrast, async-std provides a more hands-on/low-level approach. If you are unlucky enough to have libraries that choose different stacks to work on, you'll possibly (probably?) have to handle both.
Warp
-
Warp VS Wave Terminal - a user suggested alternative
2 projects | 3 Apr 2024
- Fig Is Sunsetting
-
Linux version of Warp terminal is here
I'm trying out Warp for the first time, and an immediate accessibility issue for me is that the text is simply too small to read for a lot of the UI elements (context menu, side bar, tab bar…). The size should be configurable for all of the elements, not just the terminal view. I think I would also be fine with a setting that just scales the whole UI.
I did notice there is an issue for it already: https://github.com/warpdotdev/Warp/issues/1443
- The New Terminal (Beta) Is Now in JetBrains IDEs
-
How To Change Your Zoom Background With Code
Warp is a Rust-based terminal with AI built in. I like it because it has things like autocompletions, history search, click-to-edit, and theming out-of-the-box. Feels super modern. And if you do want to try it out, use my referral link & get a free theme!)
-
OpenAI Whisper: Transcribe in the Terminal for free
Unless you want to type this every day, I’d recommend creating an alias. In my case, I’m using Warp, so I’ll right-click the command and choose Save as Workflow to save my script as a workflow. Warp AI will even help me autofill the title and description and detect variables.
-
Keystroke timing obfuscation added to SSH(1)
This makes me wonder about newer terminal emulators on maccOS like Warp[1], and if they're for example taking all input locally, and then sending it over the remote host in a single blob or not? I imagine doing so would possibly break any sort of raw-mode input being done on remote host but I'd also imagine that is a detectable situation in which you could switch into a raw keystroke feed as well.
[1]: https://warp.dev
- How Warp's terminal app brings new ideas, AI to the command line
-
AI tools for productivity
Warp - GPT in the terminal - very helpful for debugging
-
Does anyone try the new terminal emulator Warp with Neovim?
You're right, I just found the discussion there (and it's the longest one currently). For now, I just run tmux inside the emulator.
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
alacritty - A cross-platform, OpenGL terminal emulator.
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
smol - A small and fast async runtime for Rust
hyperterm - A terminal built on web technologies
futures-rs - Zero-cost asynchronous programming in Rust
hyper - An HTTP library for Rust
reqwest - An easy and powerful Rust HTTP Client
kitty - Cross-platform, fast, feature-rich, GPU based terminal
embassy - Modern embedded framework, using Rust and async.
wezterm - A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust