Vue.js vs React with pre-made components

Vue can easily be integrated with other front-end libraries. This makes it an extremely versatile tool and it's easy to fix its shortcomings or missing features by just plugging in another library.

Very useful.

Vue.js weighs in at 16kb min+gzip.

Since most of the mainstream server-side rendering implementations are synchronous, they can block the server's event loop when the application is complex.

Vue implements streaming server-side rendering, which allows you to render your component, get a readable stream and directly pipe that to the HTTP response. This allows you to have a responsive server and decreases the time your users have to wait before they get your rendered content.

Although you can build components in JavaScript files, you can also use inline handlebars-like templating in your HTML views where simplicity is often a more sane choice.

Since the template-to-virtual-DOM and compiler can be separated, you can compile the templates in your machine and then deploying only the interpreter which is 12KB minified and gzipped.

You can choose to use either a templating language, or if you feel it's necessary to drop on a lower virtual-dom level, you can use JSX. This is simply done by replacing the template option with a render function.

Or alternatively, you can embed functions inside templates by using the <render> tag.

Starting with Vue 2.0, Vue supports server-side rendering. This helps with SEO a lot, since the views are rendered directly on the server, which are indexed by search engines.

Since every single UI component is created independently in JavaScript, it becomes very easy to reuse them throughout your app without having to re-write them.

React is built by Facebook engineers initially to be used only for their inner projects especially to solve the problem of building large complex applications with constantly changing data.

Flux is a platform agnostic pattern which can technically be used with any application or programming language.

One of Flux' main features is that it enforces uni-directional data flow which means that views do not change the data directly.

With React this is useful because this way it's easier to understand an application as it starts getting more complicated. By having two-way data binding, lead to unpredictable changes, where changing one model's data would end up updating another model. By using the Flux architecture, this can be avoided.

Instead of relying on the DOM, React implements a virtual DOM from scratch, allowing it to calculate precisely what needs to be patched during the next screen refresh. This is orders of magnitude faster than fiddling with the DOM itself.

Since React's virtual DOM system is implemented completely in JavaScript, it's very easy to write UI test cases.

React is used on one of the most visited websites on the planet, Facebook. With stellar results and with million of people experiencing it every day.

ReactJS can be used independently as the only library for building the front-end, or it can be used alongside JavaScript libraries such as jQuery, or even Angular.

React's one-way data binding (or one-way data flow) means that it's easy to see where and how your UI is updated and where you need to make changes. It's also very easy to keep everything modular, fast and well-organized.

Since React v0.15, SVG is fully supported. React supports all SVG attributes that are recognized by today's browsers.

React provides a template engine (JSX) which is easy to use. But it's not mandatory.

React has an official Chrome Extension which is used as a developing and debugging tool. It can be used to quickly and painlessly debug your application or view the whole application structure as it's rendered.

React can render it's components and data server side, then it sends those components as HTML to the browser.

This ensures faster initial loading time and SEO friendliness out of the box, since it's indexed as any other static website by search engines.