This is gold & totally underrated ! Probably the best (and only) explanation of the Actor model and how to use it with XState. Can't wait to know more about XState 5 and XActor !
Worst thing about actors is how easy it is for errors or problems to just vanish, resulting in timeout errors at best or incorrect state at worst. Concurrency based on coroutines, and maybe reactive streams, are almost always easier to understand and reason about. The only exception is when the system/algorithm requires more and more synchronization primitives or interprocess communication. As I see it, actors add a lot of complexity and are only justified when latency on the order of milliseconds in a very complex system is paramount. Even then, there may be simpler and more observable ways to achieve the same goals.
This is gold & totally underrated ! Probably the best (and only) explanation of the Actor model and how to use it with XState. Can't wait to know more about XState 5 and XActor !
I completely agree
I'm still not understand the concept, lol
Worst thing about actors is how easy it is for errors or problems to just vanish, resulting in timeout errors at best or incorrect state at worst. Concurrency based on coroutines, and maybe reactive streams, are almost always easier to understand and reason about. The only exception is when the system/algorithm requires more and more synchronization primitives or interprocess communication. As I see it, actors add a lot of complexity and are only justified when latency on the order of milliseconds in a very complex system is paramount. Even then, there may be simpler and more observable ways to achieve the same goals.
"Messages are immutable"
So, when the egg collides author's head it wouldn't be broken.