You get much faster prototyping, collaborative tools out of the box and even a debugger with a timeline out of the box (you just have to save your state at every change and have a little scrollbar to scroll through your states). This is very very powerful.
The site does say:
> React Hot Loader will keep it mounted, preserving the state.
but I agree that it could be more explicit about how it's useful.
http://research.microsoft.com/pubs/189242/pldi097-burckhardt...
From the paper, adding a navigability aspect between UI and executing code is something that is fairly straightfoward to do and very useful.
My current live programming work is over stateful code (meaning the code that is being live edited involves side effects). It is difficult to support that in existing programming models, however.
This gives huge productivity boost when developing complex nested UIs because you can quickly tweak CSS/JSX without blowing away all the state (like modal windows, tabs, loaded data, etc).
So, I guess I'm looking for a technical summary of what this does exactly because I don't understand the benefit.