@paul_cardinale wrote:
It's a good architecture that makes sense in this case. While nested event structures can be susceptible to problems, it's not hard to debug such problems.
Admonitions such as "Never do this", "Always do that". are bad.
If you know what you are doing, then you can embed event structures. But anyone asking a question here about event structures generally doesn't know what they are doing with them. Before you know it, they add another event, bury another case, or a loop, and lock up their code cold. It is better to show them examples that aren't going to lead them to a path of failure.
