In this Round-up, we are taking a few closer looks at React’s interplay with different frameworks and architectures.
“Little framework BIG splash”
Architecting your app with react
React is not a full MVC framework, and this is actually one of its strengths. Many who adopt React choose to do so alongside their favorite MVC framework, like Backbone. React has no opinions about routing or syncing data, so you can easily use your favorite tools to handle those aspects of your frontend application. You’ll often see React used to manage specific parts of an application’s UI and not others. React really shines, however, when you fully embrace its strategies and make it the core of your application’s interface.
React vs. async DOM manipulation
React, Scala and the Play Framework
Nehlsen’s React frontend is the second implementation of his chat application’s frontend, following an AngularJS version. Both implementations are functionally equivalent and offer some perspective on differences between the two frameworks.
In another article, he walks us through the process of using React with scala.js to implement app-wide undo functionality.
Also check out his talk at Ping Conference 2014, in which he walks through a lot of the previously content in great detail.
React and Backbone
React vs. Ember
Eric Berry (@coderberry) developed Ember equivalents for some of the official React examples. Read his post for a side-by-side comparison of the respective implementations: “Facebook React vs. Ember”.
React and plain old HTML
React-Magic intercepts all navigation (link clicks and form posts) and loads the requested page via an AJAX request. React is then used to “diff” the old HTML with the new HTML, and only update the parts of the DOM that have been changed.
On a related note, Reactize by Ross Allen (@ssorallen) is a similarly awesome project: A wrapper for Rails’ Turbolinks, which seems to have inspired John Lynch (@johnrlynch) to then create a server-rendered version using the JSX transformer in Rails middleware.
React and Object.observe
React and Angular
Ian Bicking (@ianbicking) of Mozilla Labs explains why he “decided to go with React instead of Angular.js”.
David Chang works through some performance improvements of his ngReact project. His post “ng-React Update - React 0.9 and Angular Track By” includes some helpful advice on boosting render performance for Angular components.
Angular gives you a ton of functionality out of the box - a full MV* framework - and I am a big fan, but I’ll admit that you need to know how to twist the right knobs to get performance.
That said, React gives you a very strong view component out of the box with the performance baked right in. Try as I did, I couldn’t actually get it any faster. So pretty impressive stuff.
React was also recently mentioned at ng-conf, where the Angular team commented on React’s concept of the virtual DOM:
React and Web Components
D3 and React
Om and React
Worked for 2 hours on a [@react_js](https://twitter.com/react_js) app sans internet. Love that I could get stuff done with it without googling every question.— John Shimek (@varikin) February 20, 2014