@mejari - the reason why I wrote out the React code long-form is because I couldn't figure out how to write it concisely :) Not because I'm biased hehe.
I disagree it's not identical to React+Flux at all. There's more pieces and wiring required for the typical "Save" button example. In react+flux, the views need to listen on stores:
MyStore.listen(this._onMyStoreChange.bind(this));
The views manually call action creators:
MyActions.saveData();
Action creators dispatch separate events for beforeRequest, onRequest, onError events:
this.actions.onBeforeSaveSomething();
// do the save
this.dispatch({ type: 'SUCCESS', data: myData });
Stores need to listen for action creator events:
this.bindAction(actions.onBeforeSaveSomething, this.onBeforeSaveSomething);
this.bindAction(actions.onSave, this.onSave);
this.bindAction(actions.onError, this.onError);
In the Flux flavor I'm using (alt), stores automatically dispatch events when their state is changed, but I found managing the store state is annoying because of the loading, error flags[1].
So the store.onSave might look like this:
this.loading = false;
this.error = null;
this.data = data;
Finally, the view updates it's state in response to a store change which automatically calls render.
Then in the view render, you can show your loading/saving mask.
[1] https://news.ycombinator.com/item?id=9315503