i would agree that this is the traditional perspective.
i'm not convinced this is necessarily the case; there may be other ways to look at it. it could be that the ui "value" is the output of a series of functions, and that what might look like a "state" change is really a "new" ui being rendered.
(maybe this is what "frp" gives us, or perhaps "immediate mode gui" that sometimes pops up in game development circles; but i'm not very familiar with either.)
Real times streams aren't really meant to be handled by Flux/Redux or GraphQL. I should have said that GaphQL/Relay handles 80% of cases better than Flux/Redux! The rest require a different approach. Thoughts?
Why on earth would someone write this in a Github gist? Just use one of the billion blogging platforms out there or Github's own pages feature.
Relay sounds interesting. I expect that a lot of its good ideas will be replicated by the community in more light-weight, less opinionated libraries.