[hudbuddy]

Since no one has mentioned it yet, and it respectably isn't mentioned in the article, the author of this is the creator of the cycle.js (cycle.js.org).

It is a really cool way of looking at DOM state as a flow of: <interface> -> user interaction -> application reaction -> <interface>

The general idea being that the state of an application can be represented by a timeline of events throughout the lifetime of an application. Since it is entirely time and event driven/stateless, it gives way to some pretty cool "time travel" concepts.

The philosophy is this:

If you know how something begins, and you know the exact times at which anything happens to it, then you can assume its state at any given period in time.

[jfoutz]

IMHO, you run into the same problem as journaling. User interaction is basically a stream of deltas. If everything is perfect, it’s awesome. But really, you want checkpoints from time to time.

It’s a cool idea. It’s cooler if your organization has the chops to rarely introduce defects. Replaying on refresh works ok ish. The really cool part is making every interaction with the system uniform. State comes in, small tweak, state goes out.