> so lost their minds fleeing from the GIL that they forgot historical lessons

I just don't agree. `async def` gets the fact that we've departed Kansas, good Toto, right out front.

Async moves the coder a step in the direction of the operating system itself. The juice is not worth the squeeze unless the project bears fruit.

I hardly do enough networky stuff to make this facility useful to me, but I'm grateful to the hours poured into making it part of Python.

Contra the author of The Famous Article, threads seem gnarlier still, and I would likely architect out any async parts of a system into another service and talk to it over a port.

> I would likely architect out any async parts of a system into another service and talk to it over a port

This doesn't get you any closer to the goal though. Would you talk to the other service with a blocking socket request or a non-blocking one? A non-blocking socket request either invokes a system thread or asyncio. You can't escape that part.