The example in the EnforcePlayerTurns section is kind of buggy. Make an attempt to place two Xs in a row in different cells, then place an O in a third cell - the second X you attempted to place will magically show up at the same time as that O.
I'm not convinced. The main selling point is that developers don't have to know the previous code to make changes... complete with a precedence system.<p>Apart from seeing very little explanation why this would work, I can't help but think of a Website, where instead of replacing existing classes, we add more and more with higher specificity.
This seems to be like state machines, aside from<p>> As new ideas and requirements are discovered, we can forbid certain things from happening by simply adding new b-threads; without having to dig and figure out how earlier-written code works!<p>Which I'm not really sure is a step <i>up</i> from state machines?