/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 boats.gitlab.io
Global Executors
| | blog.dureuill.net
Naming is hard
3.9 parsecs away

Travel
| | Some Rust libraries are like oil and water, they just don't mix. With the async runtime tokio and the data-parallelism library rayon, I learned it the hard way.
| | without.boats
Global Executors
0.0 parsecs away

Travel
| |
| | blog.polybdenum.com
Fixing the Next Thousand Deadlocks: Why Buffered Streams Are Broken and How To Make Them Safer | Considerations on Codecrafting
4.4 parsecs away

Travel
| | I am fortunate enough to work on a production Rust service (a real one, not cryptocurrency nonsense). Rust virtually eliminates the kinds of stupid bugs and gotchas that are endemic in other languages, making it much easier to develop and maintain our project. Unfortunately, Rust is substantially less capable when it comes to preventing the common issues involved in async programming. In fact, async programming is substantially harder to get right in Rust than in something like Javascript, due to the decision to make task spawning explicit for performance reasons.
| | nnethercote.github.io
Benchmarking - The Rust Performance Book
26.3 parsecs away

Travel
| [AI summary] The text explains the basics of benchmarking in Rust, covering workload selection, tools like criterion, and the trade-offs between different performance metrics.