Update to React 16.0 (Fiber) eventually once it launches

[victorporof]

React Fibre most likely won't impact us, as it’s mostly internal changes with no alterations in the surface API (last time I checked). In terms of performance, we’ll likely also not see any perf wins, since

1. We're very careful about avoiding useless re-renders,
2. We don’t have long-lived renderings at all,
3. Our store updates are incremental, but there’s no avalanche of redux actions causing too many “simultaneous” rerenders due to react-redux calling forceUpdate. If this ends up happening, batching redux actions is probably the best simple solution.

On the future, however, it’s probably expected for new apis to surface, and new patterns emerging, which might make an impact on how we write our components, and maybe even the high level browser architecture (putting more stuff in workers? OTMT component "rendering"?).

At this point, we're likely to continue benefitting the most from simply using immutable data structures and pure components.

[victorporof]

http://isfiberreadyyet.com

[victorporof]

Throttling updates to subscribed clients no the redux store is done in https://github.com/victorporof/tofino/pull/82