Scheduling in React
There's definitely some very cool work here... I do think that it's important to remember that the simplest solution is usually the best one to start with.  I typically start with redux and redux-thunks with react apps, mostly because I will nearly always hit a point in complexity where it is worth separating state management from the main UI, and thunks is the simplest extension to support async interactions to a server.<p>From there, debounce or concurrent interactions are probably an easier stopgap first.  At least until these APIs are distilled a bit, and abstractions make them easier to work with.<p>This can all be summed up with: YAGNI and "Don't prematurely optimize"  I've only had a handful of cases where I had to make things more difficult because of behavioral issues in browser applications.