[ffn]

Honestly, though, Tomster v. electrons-circling-nucleus branding aside, both ember and react are currently experiencing a lot of community-driven convergence in core philosophy.

For example, ember-redux exists to take the functional centralized state-management of redux that makes react great and ports it to ember. Similarly, react-scripts takes the developer-ease of ember-cli and gives it to react. Everybody uses the DDAU for handling DOM interaction, shadow-dom-tree-diffing (or whatever it's called) for rendering, some sort of declarative remote data-layer in both ember-data and redux-orm (and there's even ember-redux-orm), and junk like animation-handling and whatnot all expose the same change-attribute-yield-block API to the programmer.

If you look beyond the stylistic difference of things like writing jsx v. hbs, there's actually very little philosophical difference between modern 2.x ember and modern react

[acemarke]

Nitpick: Redux-ORM is _only_ about managing relational data in normalized form locally. (Technically, it's not even Redux-specific - you can hand it any plain JS object to work with.) It doesn't do any remote requests or syncing.

That said, it's a great abstraction for handling relational data, and I'm a huge fan of it.