React contexts enable information sharing between components. However, they aren't always the best fit for a project. See why and how to properly use them.
How to make a React component independent, notify its parent when its the state changes, and enable the parent to pass down new state at any time.
Using state tables for testing is great for situations where there are a variety of inputs for a function that produce different results.
In several projects that I have worked on over the last few years, we instituted a StateHolder class that eases the burden of managing state.
Ember and Ember Data don't have the greatest dirty state tracking, but you can easily add it in yourself. Don't lose your form data!
It's amazing how easy it is to build sophisticated apps with Ember. This post explores one feature of Ember that enables this: pervasive data binding.
My top three Clojure lessons: sequester mutable state; think functionally and be idiomatic; and practice, practice, practice.
The problem with the CGI way is that the state of your application is bifurcated between client and server and exists in different places at different times