zlacker

[parent] [thread] 3 comments
1. ameliu+(OP)[view] [source] 2024-01-23 13:30:37
Yes, async is easier, but granularity of performance is a real downside. The CPU is a resource too, and needs to be managed more carefully than async can do. There's a reason why people stopped using cooperative multitasking like in Windows 3.1 ...
replies(1): >>the_mi+j6
2. the_mi+j6[view] [source] 2024-01-23 14:07:56
>>ameliu+(OP)
Sure, but that’s not really an argument for or against async but for or against different runtime policies.
replies(1): >>ameliu+IL
◧◩
3. ameliu+IL[view] [source] [discussion] 2024-01-23 16:56:26
>>the_mi+j6
What good are "runtime policies" if you're in a single thread that you can't interrupt (which is what async is)?
replies(1): >>the_mi+m62
◧◩◪
4. the_mi+m62[view] [source] [discussion] 2024-01-23 22:54:08
>>ameliu+IL
Async is not really that in Rust. While it's true that a singular poll cannot be preempted, things like task::spawn schedule that on a multi threaded executor. So a lot of cases behave just like threads except you await them from somewhere else.
[go to top]