Synchronous functions like time.sleep() halt the execution of the current thread. In an asynchronous context, which relies on a
single-threaded event loop to manage multiple tasks concurrently, calling time.sleep() blocks this entire event loop. When the event loop
is blocked, it cannot switch between tasks, process I/O events, or respond to other operations. Consequently, all other concurrent asynchronous tasks
are paused until the time.sleep() call completes. This effectively negates the benefits of using async/await by turning a
non-blocking operation (waiting) into a blocking one that freezes the application’s concurrency model.
For instance, if an asynchronous web server uses time.sleep() in a request handler, it won’t be able to process any other incoming
requests until the sleep call completes, leading to poor performance and responsiveness.
The correct approach in asynchronous programming is to use non-blocking sleep functions provided by the specific asynchronous framework being used
(e.g., asyncio, Trio, AnyIO). These functions give control back to the event loop, allowing it to run other
tasks while the current task is "sleeping".
