News for hackers. Stuff that matters.

A comment on Fast, Safe, and Complete(ish) Web Service in Rust. Parent comment

Re:Fast, Safe, and Complete(ish) Web Service in Rust by zzzcpan on Tuesday March 27, 2018 @05:08PM (#16692734)
Any process or thread can be descheduled by the OS on top of the stuff it does on its own.

Yielding is a thing from the multithreaded world with synchronous APIs. Asynchronous systems don't yield, they are programmed asynchronously. They have no yielding overhead and can never be slower than yielding threads.

If you are arguing for 1:1 kernel threading against M:N threading (coroutines, goroutines, green threads) that's fine, but multithreading implementations have absolutely nothing to do with asynchronous systems.

[ Parent | on HN ]
Re:Fast, Safe, and Complete(ish) Web Service in Rust by zbentley on Tuesday March 27, 2018 @06:40PM (#16693467)
It seems like the two of you disagree fundamentally on what "asynchronous" means in this context.

https://en.wikipedia.org/wiki/Asynchrony_(computer_programmi...

[ Parent | on HN ]
Re:Fast, Safe, and Complete(ish) Web Service in Rust by zzzcpan on Tuesday March 27, 2018 @09:35PM (#16694451)
I don't think we disagree on that, since he explicitly mentions event loops and essentially claims they are generally slower. Which is nonsense.
[ Parent | on HN ]