SetState, We Need to Talk!
summary
Argues finite state machines remove unpredictable UI bugs by centralizing logic, demonstrates a small login form refactor into an explicit state machine that runs correctly in the demo, and shows race conditions disappear when the UI can only be in one state. Counts the combinatorial problem — 2^3 = eight possible permutations — to justify the change. Recommends trying xtate for minimal boilerplate, models states like isLoading and transitions like submit_form for clarity.
AI-written summary · about
chapters (4)
related talks
28mState machines for frontend state management
25mMastering UIs with Finite State Machines
32mFormal Forms with State Machines
45mState of the Art User Interfaces with State Machines
30mMastering UIs with Finite State Machines
34mState Machines Meet React Hooks
38mInto the Visual World of State Machines
29mCrafting Stateful Styles with State Machines