@jarrodwatts Probably the most epic career change ever!
The game was against a German, not Danish player.
You can find the whole game with an incredible end game here https://t.co/pEGwBJ8bMu
@DavidKPiano The best part is that you can easily abstract postMessage away, so for you system it's just another actor that you can send events to.
I love the actor model!
What if your state machine could do heavy computation without blocking the UI?
Inspired by my feature request for @DavidKPiano's wishlist, I moved an XState machine into a worker.
Same machine. Zero main thread blocking.
Actor model + FSM + Web Workers = π₯
@DavidKPiano Lastly, not sure if anyone has experimented with this before but there are some actors that are computationally expensive and not directly tied to UI. A spawn option to get them into another thread and easy abstraction over postMessage so you don't need to think about it πββοΈ
If you're not using XState yet, now is the perfect time to learn it. If you can write code like NASA with incredible tooling & type safety, why are your web apps full of bugs and horrible performance?
Once you understand the actor model and finite automata, you can never go back
@DavidKPiano For Christmas I also wish for an xstate based frontend framework with O(1) deterministic updates. No reconciliation, no useEffect but still based on JSX. The performance would be insane and would eliminate so many sources of bugs