React, Flux, GraphQL, Hack, HHVM...? All of this and more!
React.js and the accompanying ecosystem has gained huge momentum since it's launch in 2013. During 2015 the ecosystem was in a constant state of change and Angular was amidst a huge change. So now midway through to 2016, what should you choose and why?
Many React projects are starting to standardise on Babel, WebPack, Redux and React Router. Meanwhile the Angular team has been doing big strides to modernise their framework. Angular 2 has now reached Release Candidate status and it's maturing fast.
Angular continues on the path of being a complete application development framework, where as React itself continues to be a UI library with many associated projects for application development.
Both React and Angular are embracing the use of components, so in this way both are very similar to each other. Unfortunately neither of these is a straight implementation of any standard like Web Components as those are not yet mature and feature complete enough.
Out of the two Angular 2 is definitely more of a product. It's a complete set of components tied together in a certain way. With the Ember.js inspired Angular CLI tool it's easy to setup a uniform layout for a project that is built by the recommendations of the development team itself, straight out of the Official Angular 2 Style Guide.
As mentioned earlier the React ecosystem has matured significantly in the last year with a few prominent supporting elements that are de-facto usability. With much of breaking changes behind us in the world of React Router and such, the developer experience for new developers is bound to be better.
Both projects are backed up by corporate giants (Facebook and Google) and will be around for years to come. React has a massive user base, but as a new project Angular 2 also boasts a strong brand and a large developer base currently using Angular 1.
Currently the only sure fire way to lose is to use both React.js and Angular 2 on the same project.Tweet