Vue.js vs Inferno

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.

Use it however you want in a framework of your own custom design. When things change in the industry, swap things out instead of being locked in by someone else's design.

Inferno weighs in at 9kb gzipped, which is light-weight.

Inferno is one of the fastest UI libraries around and widely considered the fastest.

Using the Inferno compatibility package ("inferno-compat"), Inferno can support the vast majority of React codebases.