Mech looks really interesting! Does it handle cycles in the data dependencies? I find this usually to be the crux of the reactive model.
That said, one of the things I'm really interested in is seeing how far I can take the model on a DAG, because programs are much easier to reason able when they don't have cycles in the data. So far it seems you can write some very complicated programs (games, graphical user interfaces, robotics) as a DAG.
I've been trying to write a game and I always keep running into cycles. You're right, a lot can be done as a DAG, but especially for games, cycles happen a lot.
I'd love some resources on how to deal with those cycles when they come up.