On the react and angular

React research, the motive force is not virtual DOM and response speed, but the spirit of react native to go.

Feel react design bad, did not separate html,js, but mixed together, each new design components such as TESTDIV, must be executed under React.render to render, and to indicate the container containing the component, such as the ID of the example Div. This implementation of a large project results, very not intuitive and cumbersome, I really do not understand how FB is thinking

React.render (
<testdiv data={{name: ' React ', value: ' Haha '}}/>
document.getElementById (' example ')
);

Instead, angular custom directives, just need to be semantically embedded in HTML pages, such as <div id= "Example" ><TestDiv></TestDiv></div> just fine, The real implementation of the HTML and JS separation, retaining the development habits of the front-end developers, and the data is two-way binding, unlike react to pass props one-way binding and state bidirectional change, the whole design ideas clear and simple

If it were me, I would modify the react into a custom component like angular (Directive) embedded in the native HTML semantic tag class, and then use the program to identify and render the render in bulk, rather than to the developer one by one of their own render. FB needs to improve the user experience, for development tools, know that developers are users.

On the react and angular