There's No Such Thing As Local State

This post is part of a series of corollaries to the Inglorious Web series . It stands alone, but the examples make more sense if you've read the architecture post first. There's a decision every frontend developer makes early in a project, usually without realizing it's a decision: where does state live? It feels like a technical question. It's actually an architectural one. Most frameworks default to local state and make global state expensive. Inglorious Web flips the default: state is global unless you intentionally isolate it. The difference looks like this: Every mainstream approach has a point where the model strains. The strain always comes from the same place — state that was supposed to stay contained, didn't. Here are three projects, three frameworks, and three different versions of why that matters. Fattutto: Context API Hits Its Limits In 2018 I was hired as lead front-end architect on Fattutto , an invoicing application. We were a small team — two front-enders, two back-en