I'm still puzzled people choose react over W3C HTML standards like web components. It just doesn't make sense unless you want to support IE9/10.
Basically, Web Components exist to solve a different problem than React.
> WebComponents provide strong encapsulation for reusable components, while React provides a declarative library that keeps the DOM in sync with your data.
You can use something like reflux with web components to do this too. The fact that react uses virtual dom is an implementation detail I think.
Maybe I'm missing something obvious here.
Even react tutorial operates with components: https://facebook.github.io/react/docs/tutorial.html
Well that is just entirely pretentious.
This is a verbose re-statement of components, which are not new.
Before React, you couldn't do this in a performant, UX-positive way
Has there never been a performant component based UI framework?
Contrast this with two previous approaches. The first is where you have a component hierarchy that renders the initial state of the view, but when the data changes you need to write imperative code to transition the native views to reflect the new state. The second is traditional data binding, which doesn't help when you want to change the view hierarchy itself (rather than properties of existing views) based on an underlying data change.