Cool! The "why" section doesn't do a great job IMHO of explaining why this is interesting when we already have asyncio; the tutorial does a better job of showin

Cool! The "why" section doesn't do a great job IMHO of explaining why this is interesting when we already have asyncio; the tutorial does a better job of showing off capabilities that are unique to this library. The key is that in most async libraries (including asyncio), the event loop sees the world as a collection of independent callbacks, which makes it very difficult to inspect and debug the system. Curio is modeled more like a thread/process scheduler that knows about the sequential tasks taking place at the higher level, so it can provide debugging tools similar to what you'd see in a multithreaded debugger.