Async/await

No fear of getting old.

Async in the air.

New frameworks in sight.

Geeky rap on deck.

It's a great way to support the podcast.

Another aspect certainly is that Stackless had become like a sort of niche project in the ecosystem overall.

With Python 3, we have AsyncIO built on the Twisted model.

And even in the Python 2 world, gevent had become a lot more famous than Stackless Python, presumably because you could just import gevent in a standard C Python interpreter, while Stackless Python is more complicated to get started with.

Overall, the sentiment was highly positive, viewing Logo as a foundational language that inspired many careers and educational approaches.

Title, A Design Space Exploration of Async Await.

Source, cell.cs.br own.edu.

The article analyzed how Async Await works differently across modern programming languages.

It explained that there are many design decisions, such as when tasks are started, how long they last, and how cancellations are handled, which vary from language to language.

The author introduced a formal model that helps explain why the same code produces different outputs in different runtimes.

Overall, the article highlighted the complexity of async await systems and the importance of understanding their specific design choices.

In the comments, the community mostly supported the work, praising its thoroughness and usefulness for understanding concurrency.

And people can decide, like, hey, you don't, you dislike, like, one notation? Sure, just use the other one.

But, yes, like, let's say for people familiar with AsyncIO, the syntax, like, the AsyncAwait syntax is very similar to AsyncIO.

So you basically have your coroutine, so your syncdef, whatever you want, and you await primitives or stuff.

So the main difference is that instead of importing stuff from AsyncIO, so like, I don't know, sleep or timer or whatever, you import similar primitives from Tonio.