> Any time you call a blocking function that the system provides, it should immediately yield the fiber, which makes it look preemptive.

Makes sense. It let's you avoid the quite verbose and incompatible async/await syntax.

---

> The author was talking about different methods for handling more than one request at a given time, which include forking and threads

I feel like if the author suggests forking, he should also provide a way for reliable robust message passing, like erlang.

---

Thanks for such a detailed explanation. I wish more languages supported Erlang style processes. That are green, preemptively switched and multi-core!

Do you have any experience writing such systems? I was thinking to experiment with the cpython interpreter.