We know that modifying and querying Document Object Model could be a major performance bottleneck in web mobile application development. If I had to single out one reason to use React it might be precisely the optimizations in that namespace.
Here comes a shocker – however keep on reading – React isn’t AN MVC framework! Optimized for one-way binding (or unidirectional data flow) Models in the sense notable to Backbone or Sencha touch aren’t present in React. Fear not, two-way binding primarily happens in sort of events triggered by a amendment in part state. Here we introduced a element, that may be a mixture of view and Controller. With this notion in mind it’s hard not to notice that something almost revolutionary is going on here. i will be able to discuss elements any down within the DOM section.
As everything revolves around elements, therefore will the class system. perhaps it’s valid to mention that element makes it’s own class (eco)system. elements area unit designed with Abstraction in mind, one among the most unremarkably used ways will be React.createClass. However, with lack of traditional MVC, traditional class system becomes obsolete as well.
Third party plugins
The market of third party plugins for React remains scarce. helpful extensions that bridge React with Angular, Backbone, and even ClojureScript are amongst the popular few. Follow the official blog to find out regarding the upcoming plugin releases.
For a young framework, documentation is full of helpful guides and tips, specifically what new developers need to begin on the correct foot. Hopefully a lot of external learning resources also will emerge within the months to come.