dnlgl

My strong guess is that they have just reinvented a client component of an eventually consistent data store, and in this context the blogpost is actually embarrassing for them. I wonder if they will notice further problems and reinvent causal consistency and vector clocks next.

Quite the opposite, actually. He said that he will probably be fired, but should still insist on it being the right way: "Any coding standard which insists on syntactic clarity at the expense of algorithmic clarity should be rewritten. If your employer fires you for using this trick, tell them that repeatedly as the security staff drag you out of the building." https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html

It is already all but known to be quasi-polynomial, thanks to László Babai: https://www.quantamagazine.org/graph-isomorphism-vanquished-...

State machines are at the core of event-driven programming, but I often find coroutines to be a better, cleaner alternative. See this HN thread: https://news.ycombinator.com/item?id=7676691