4 ms·
I can't overstate what a gamechanger state based development using XState + React with hooks has been for me versus a standard Redux/Flow architecture with clas
by aphextron 7y ago
I can't overstate what a gamechanger state based development using XState + React with hooks has been for me versus a standard Redux/Flow architecture with class based components. It allows you to extract business logic from your components to the point that React becomes nothing more than a view rendering layer. This makes it way easier to understand the flow of your application and simply read through the statechart and look at the corresponding components for each state. No more parsing through giant component class files, dealing with lifecycles, or mixing logic with presentation. It allows you to build a fully deterministic UI where bugs become almost impossible to happen.
- davidkpiano 7y agoThat's awesome to hear! (Author of XState here) For those curious: XState is a JavaScript state machine/statechart library that doesn't invent any new concepts and instead adheres strictly to statechart principles and the SCXML spec.
- spiffytech 7y agoHow have you managed keeping your machine's state and context consistent? Although I can control transitions easily, I've found it's easy to miss updating parts of my machine's internal context when wiring up transitions. I wind up with my component thinking it's in a particular State, with a context that doesn't match up.
- jlu 7y agoIsn’t that the job of actions after an transition happened? (modifying the internal context according to the event).
- spiffytech 7y agoIt is indeed. However, I've found the problem of writing assignment actions correctly is very similar to the problem of managing ordinary variables without xstate. I'm wondering if I'm doing this right, since I thought xstate was supposed to make that kind of bug much rarer.
- candeira 7y agoYes! Extremely same, but with Vue instead of React. In the last project I worked on, XState was a late addition, so it didn't control the whole application, but the part I wrote in it was bug free from the start. My plan for any future JS/frontend project is to design the whole application's business logic around XState, and use Vue/React/Svelte/Whatever just for the rendering part.
- james_s_tayler 7y agoThis sounds very interesting! Do you have a link to a repo or tutorial / good reference example?
- HerrBertling 7y agoOh, that would be awesome! I’m very interested as well :)
- candeira 7y agoNo, sorry. This was contract work, and is closed source.
- james_s_tayler 7y agoThat's ok. Anything publicly available you used as reference materials? I had a read through that site, but id love to see what's considered a good example in code.
- candeira 7y agoFrom memory, one of the things we did was set up an event bus to communicate between xstate and Vuex. We only used the xstate.org.js and vuejs.org documentation, which are both very good. Sorry I can't help further.
- beardedman 7y agoWould love a real world example of this. Building a smaller application is fine - but what does XState look like in an enterprise level context?