XState is amazing, but one thing developers I work with are getting stuck on is that there is too much choice in how to model. There is too much learning and trial and error just in this, and then they get frustrated if they (for example) end up writing a lot of scaffolding in React to get context in a spawned machine that could be in the parent. 2 minute videos of non-dev best practise tips alongside the developer docs would help guide newcomers!

https://twitter.com/aceslick911/status/1526513266691756033

Example: Excel https://twitter.com/jamestharpe/status/1179732994283769858?s=20&t=S0okSRHdWum4Qyhj4Y3WtQ

Define the best approach way from Parent Actor to Child Actor instead of forward and introducing a new property. Keep Children Components simple and pure so that doesn't must be known outside of context. Refer the official example: https://xstate.js.org/docs/tutorials/reddit.html#spawning-subreddit-actors

https://twitter.com/broerjuang/status/1524779630745358336

https://twitter.com/haywirez/status/1179449997114400769?s=20&t=S0okSRHdWum4Qyhj4Y3WtQ

> Is there an example of syncing the machine state between browser tabs? not browser tabs specifically, but I'd like to see how to sync a machine's state on two different instances of an app. https://twitter.com/alirezavlizade/status/1615661232530366464

hope the example will be complex enough to show why need @xstate/test