|
|
|
|
|
by jokethrowaway
1481 days ago
|
|
There are two things to mention: 1. Async for trivial things is straightforward and easy 2. Rust actively discourages some async patterns to protect you from some memory misuse edge cases It does limit your freedom in writing code that eg. relies a lot on async callbacks, but there's a reason.
The first time I did a massive async project (think a rust binary maxing all cores executing the largest possible number of async fns doing various things in parallel - from fetching data online to running tensorflow) I came at it all wrong and wrote something that would have worked in node or haskell but that was a pain to compile in rust. After days of pain I understood what rust wanted and nowadays I use the same pattern and it's fairly easy for me. Just another tool in the shed. |
|