What is the best alternative to Inferno?

Question

Built By the Slant team

Find the best product instantly.

4.7 star rating

Try it now - it's free

score 101 · Answer 1

Polymer

Top Pro

Various basic components

It provides a base component. See More

Top Con

No server-side rendering

Polymer does not support server-side rendering. This results in higher loading times, more HTTP requests and it's not very SEO friendly, since search engines have no way of indexing a page if it's not rendered in the server. See More

Top Pro

HTML markup is not string

HTML markup as it can be a non-string. See More

Top Pro

Flex layout components

It provides Flex layout components. See More

Top Pro

CSS is easy to apply

CSS can be applied far more comfortably than React. See More

Top Pro

No need for special debugging tools

The presence od specialized debugging tools are advertised by competitors. The all features of web components are natively supported by browser embedded development tools. See More

Top Pro

Excellent routing

The router is embedded into CLI for project creation and covers as web as Progressive web app, also fused with Polymer layouts out of the box. The shop template for CLI has a complete solution including the routing. See More

Top Pro

Complete web app stack support

Full app stack from data tier to routing, progressive web app, responsive layouts makes no need to seek outside of Polymer ecosystem for application features. In addition to waste set of mature web components in Polymer Elements along with Vaadin Elements there are thousands of web components in the wild comparable to jQuery plugins set. See More

Top Pro

Excellent documentation

Polymer guides you as with tools (cli, build environment, app templates,..) as with complimentary documentation on all phases of app development from creation of app as progresive web app to production deployment instructions. As Polymer is standards based, the whole community around those standards also helping in documentation and support. See More

Top Pro

Based on web components

Web Components are a collection of specifications released by W3C as a way to reduce the complexity of web apps by creating reusable components. Browser support is currently poor for web components, however Polymer is developed to make web components compatible with modern browsers. See More

Top Pro

API is easy to understand, based on standard

The Polymer APIs are split on application layers and follow standards on all possible ways: Web Components, CSS variables, async API via Promises and so on. See More

Specs

v1.0 GZipped size:53K

v2.0 GZipped size (Edge):36K

v2.0 GZipped size (Safari):13K

v2.0 GZipped size (Chrome):10K

See All Specs

See All Experiences

101 22

score 520 · Answer 2

Vue.js

Top Pro

Can be used with any front-end stack

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. See More

Top Con

Poor typescript support

Very basic typescript support. See More

Top Pro

Single file component

Very useful. See More

Top Con

Very enterpris-ey in design and tooling

Top Pro

Lightweight

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

Top Pro

Vuex store, events system

Top Pro

Reactivity system

Top Pro

CLI and Webpack integration

Top Pro

Responsive server-side rendering

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. See More

Top Pro

Supports inline templating

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. See More

Top Pro

Can be made even lighter

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. See More

Top Pro

Support for both templates and JSX

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. See More

Top Pro

SEO friendly

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. See More

Top Pro

VueRouter

Specs

GZipped size:~30KB

Repository:https://github.com/vuejs/vue

See All Experiences

520 128

score 54 · Answer 3

Webix

Top Pro

A lot of widgets

Webix is one of the most extensive UI component libraries, second only to Sencha ExtJS. Not only considering the number of widgets, but also the API methods for manipulating these widgets. See More

Top Con

Commercial license

It's not free for commercial applications. See More

Top Pro

Views can be constructed using JavaScript without HTML

The most common way of working with webix is to create a JSON configuration of your view in JavaScript. When you use TypeScript, you get complete typechecking and intellisense in your IDE. See More

Top Con

Not very popular

Not really a reason to not recommend it. But it has still a small user base. It deserves a lot more attention. See More

Top Pro

Seems to be quite stable

Even the most complicated GUIs are bug-free most of the time. See More

Top Con

Not modular

The library is not modular (except for some additional more complex widgets). If you only need a few widgets, you still need to include the entire library. See More

Top Pro

Webix Jet

The webix Jet library adds all the required features for SPA development (routing, template loading, ...) See More

Top Pro

Extremely simple to implement.

To get started is extremely simple. It has a low learning curve. See More

Top Pro

Mature project

Regular updates and releases. See More

Top Pro

Great support from the webix team

The company behind webix is really quick in answering any questions you have on their forum or via email. See More

Top Pro

Awesome responsive material skins

Great design and icons pack. See More

See All Experiences

54 4

score 10 · Answer 4

Deku

Top Pro

Functional

Functional approach. See More

Top Con

No support for legacy browsers

Deku does not support legacy browsers, or relatively old browsers for that matter. They only support the latest versions of the major web browsers. See More

Top Pro

Server side rendering

Deku 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. See More

Top Con

Not a lot of learning resources

Since it's a rather new library and has a small community, there are not many examples where you can learn from out there. There are also few guides and the documentation is not amazing and has some parts that should be covered better. See More

Top Pro

Easy to learn

Since Deku is very lightweight and has a rather small API, there's not much to learn. It's pretty easy to get started and build something with it. See More

Top Pro

Can use JSX

Developers using Deku can choose to also use JSX if they want to. This is especially helpful for people who are moving from React to Deku. See More

Top Pro

Good performance

Deku's diffing algorithm is considerably faster and performs better than most libraries. The dbmonster performance mini-app written in Deku renders roughly 16% faster than other libraries. See More

See All Experiences

10 2

score 198 · Answer 5

Aurelia

Top Pro

Out of the box Typescript support

Full support for Typescript built in See More

Top Con

No big success stories yet

There are no notable big web products build with aurelia yet See More

Top Pro

Good binding system

Clear, intuitive and HTML/SVG compliant binding syntax. Examples: Default binding => value.bind One Way binding => value.one-way Two Way binding => value.two-way One Time binding => value.one-time See More

Top Con

Needs more support from the community

It would be great to have a lot of plugins made by the community, or video tutorials from experiences when using it. Hopefully in the near term future. See More

Top Pro

Conventions over configurations

Configured to give you the most common use cases by convention, which means you only need to change the default configuration for edge cases. This means that for normal cases far less boiler plate code has to be written. See More

Top Con

Two-way data binding is often considered an anti-pattern

Two-way data-binding means that a HTML element in the view and an Angular model are binded, and when one of them is changed so is the other. One-way data-binding for example does not change the model when the HTML element is changed. This is a rather controversial subject and many developers consider two-way data binding an anti-pattern and something that is useless in complex applications because it's very easy to create complex situations by using it and being unable to debug them easily or understand what's happening by just looking at the code. See More

Top Pro

Out of the box ES6 support

Aurelia includes native support for ES6 and even comes with a Gulpfile which helps with transpiling ES6 code to ES5. See More

Top Pro

Allows developers to build their application however they want

Aurelia is extremely unopinionated and was designed to be highly modular. This gives the developer the freedom to develop their application however they want, without forcing them in paradigms or rules predefined by the framework. Likewise, any of the individual components can be swapped out if so desired. See More

Top Pro

Standards compliant

Aurelia developers always try to keep within existing and emerging Web Standards, making it easier for developers to follow best practices in web development. See More

Top Pro

Agnostic code

Most of the code you write is Aurelia-agnostic. It's one of the closest libraries that you'll find to basically write plain-old, vanilla Javascript or TypeScript code (classes) and doesn't polluate your HTML/SCSS. That way you can easily test it, switch to another implementation and make it look clean (business oriented). Even the HTML. See More

Top Pro

Easy to learn

Learning aurelia basically means learning EcmaScript and HTML, since aurelia is designed for standards compliance. Also, aurelia embraces upcoming ES language features by convention, such as ES class decorators for dependency injection, encouraging clean architecture and future-proof code. See More

Top Pro

Variable binding helps with self-documenting the code

The syntax used to bind variables within the application class is very similar to Javascript itself. You can specify the type of the binding you are using explicitly, which practically self-documents your code and makes it easy to understand whether a value is one-way or two-way binded. See More

Top Pro

Structure

Aurelia.js consists of modules that can be used as a full framework or separately. See More

Top Pro

Great documentation

One of the most crucial pieces of any new technology or framework is the documentation. At present even though Aurelia is pre-beta, the documentation is pretty complete. There are code examples missing and whatnot, but for the most part it is concise and makes the main parts of the application easy to understand. See More

Top Pro

Full commercial support

Aurelia is officially backed by Durandal Inc. and has commercial and enterprise support is available. See More

Top Pro

Data binding choices with sane defaults

Aurelia defaults to one-way data binding, alining with conventional wisdom. However, there are times when two-way data binding proves useful, such as binding an input widget with a view-model. Aurelia makes two-way data binding available to developers and uses it by convention when appropriate. See More

Top Pro

Plays well with other frameworks

Aurelia can be used alongside of React and Polymer, since it is designed for interoperability. In practice, this means Aurelia developers can use React components by including an Aurelia custom element: https://github.com/Vheissu/aurelia-react-example/blob/master/README.md It also works well with Polymer, since they are both based on the WebComponents standards: http://aurelia.io/hub.html#/doc/article/aurelia/framework/latest/integrating-with-polymer See More

Top Pro

Powerful helper CLI available

https://github.com/aurelia/cli The CLI helps rapid creation of projects with generators, building, deploying and hot reloads. Webpack should be coming soon. See More

Top Pro

Growing community

The Aurelia community is growing at a great pace. Still doesn’t rival the big players line Angular or React, but the answer to an Aurelia issue is a quick question away on their Discourse. See More

Top Pro

Provides dependency injection

With dependency injection, you can load in extra javascript and new functionality just when you need it. This is particularly helpful with testing as you can swap out services for test services. It also means in single page apps you can load dependencies only as you need them instead of loading them up all up at the start. See More

Specs

GZipped size:~67kB

Repository:https://github.com/aurelia/aurelia

Minified size:~237K

See All Experiences

198 29

score 26 · Answer 6

Preact

Top Pro

Lightweight

The size when gzipped is only 3kb, and performance is as good as (or even faster than) React itself. See More

Top Con

Difficult to learn

You need to be good in React JS first to learn Preact. Documentation is not rich. And some of the examples given on site are not working. Developers are not much active on Stack Overflow as well. See More

Top Pro

Same API as react

Avoids having to learn an entire new paradigm, and makes it easy to switch between the two libraries later on. See More

Top Pro

Lots of examples and libraries

They have a bunch of examples and addon libraries. See More

Top Pro

Awesome CLI

Preact CLI gives you a perfect scoring PWA out-of-the-box with no configuration. See More

Specs

Current stable version:8.1.0

GZipped size:3.3kb

Site:https://preactjs.com

26 6

score 29 · Answer 7

Marko Widgets

Top Pro

Very fast on the server

Using Marko and Marko Widgets to render UI components on the server was shown to be 10x faster than React. A benchmark application was built using both Marko+Marko Widgets and React and the results of rendering a page of 100 search results on the server was measured and compared. Both the Marko Widgets code and the React code used a very similar UI components-based appraoch. See More

Top Pro

Stateful UI components

Marko Widgets supports stateful UI components. Marko Widgets will automatically rerender a UI component if its internal state changes. A UI component's state is stored in the this.state property that is a vanilla JavaScript object. All changes to the state should go through the this.setState(name, value) method (or this.replaceState(newState)) See More

Top Pro

Very fast in the browser

Marko Widgets utilizes the morphdom module for updating the DOM and that module was shown to be very competitive with React and virtual-dom. See More

Top Pro

The real DOM is the source of truth

Marko Widgets does not rely on a virtual DOM abstraction. Instead, the real DOM is always the source of truth. When updating the DOM, the newly rendered DOM is compared with the real DOM. See More

Top Pro

DOM diffing/patching

Marko Widgets updates the DOM using a DOM diffing/patching algorithm to minimize the number of changes to the DOM when rerendering a UI component due to state changes. The DOM diffing/patching is handled by the independent morphdom library. See More

Top Pro

Simple JavaScript API for rendering a UI component

The following code illustrates how the render(input) method exported by a UI component's JavaScript module can be used to render a UI component and insert the resulting HTML into the DOM: require('./app-hello') .render({ name: 'John' }) .appendTo(document.body) See More

Top Pro

Batched updates

Updates to the DOM are deferred until all state changes have completed for the current tick. That is, changing a widget's state will not cause the UI component's DOM to immediately be updated. See More

Top Pro

Declarative eventing binding

Marko Widgets offers a simple mechanism for declaratively binding DOM event and custom event listeners to widget handler methods. For example: <button type="button" w-onClick="handleClick"> Click Me </button> And then in the JavaScript: module.exports = require('marko-widgets').defineComponent({ // ... handleClick: function(event, el) { this.doSomething(); } }); See More

Top Pro

Marko templating engine for the view

Marko is a fast and lightweight, general purpose HTML-based templating engine that compiles templates to CommonJS modules and supports streaming, async rendering and custom tags. Marko is used for rendering UI components and Marko Widgets is used to bind client-side behavior to rendered UI components. Marko can be used independently of Marko Widgets and this makes it suitable in all situations where HTML rendering is needed. See More

Top Pro

Efficient binding of behavior for UI components rendered on the server.

When utilizing server-side rendering of a UI, Marko Widgets does not require that the UI be rerendered again in the browser just to bind behavior. Instead, extra information is passed down from the server to the client to allow Marko Widgets to efficiently bind widgets to UI components rendered on the server. See More

Top Pro

Lightweight (~10 KB gzipped)

The runtime for Marko Widgets is extremely small. The runtime is very small and this makes Marko Widgets much simpler and easier to understand and debug. Marko Widgets offloads much of the work and complexity to compile time code so that the work required at runtime is minimal. See More

Top Pro

Easily reference nested DOM elements and nested widgets

Marko Widgets supports the concept of "scoped" IDs. With scoped IDs, a nested DOM element or nested widget can be given an ID that is unique within the scope of the containing widget. At runtime the actual ID will be the scoped ID prefixed with the ID of the parent widget. A reference nested widget can be obtained using the this.getWidget(scopedId) method and a reference to a nested DOM element can be obtained using the this.getEl(scopedId) method. For example: <div class="my-app" w-bind> <button type="button" w-onClick="handleButtonClick"> Click Me </button> <alert-overlay visible="false" w-id="alert"> This is a test alert. </alert-overlay> <div w-id="clickMessage" style="display: none;"> You clicked the button! </div> </div> And then in the JavaScript code: module.exports = require('marko-widgets').defineComponent({ // ... handleButtonClick: function(event, el) { var alertWidget = this.getWidget('alert'); // Call the `show()` function implemented by the alert widget: alertWidget.show(); var clickMessageEl = this.getEl('clickMessage'); clickMessageEl.style.display = 'block'; } }); See More

Top Pro

Efficient event delegation

Marko Widgets supports efficient event delegation to avoid attaching DOM event listeners to each DOM node. Instead, Marko Widgets attaches event listeners on the document.body event for events that bubble. Events captured at the root are efficiently delegated out to widgets. See More

Top Pro

UI components can be embedded in a Marko template using a custom tag

The following code illustrates how a UI component can be embedded in a Marko template: <div> <app-hello name="Frank"/> </div> See More

Specs

GZipped size:39.1 kB

See All Experiences

29 10

score 128 · Answer 8

Riot

Top Pro

Minimal DOM operations

Riot takes the expressions from a DOM tree and stores them in an array. Each of these expressions points to a DOM node. On each cycle these expressions are compared to the values in the DOM. So when a value has changed, Riot automatically updates the corresponding node. This way the operations are kept to a minimal amount and since the expressions can be cached, going through 1000 of them takes less than 1ms. See More

Top Pro

Lightweight

Riot is made to be used with websites of any kind, so it's built to be easy and lightweight, but still maintaining all the needed features for a UI library. It's only 2.5 KB in size when minified. So it can also be used for mobile web apps without requiring much bandwidth to download. See More

Top Pro

Components use familiar HTML tags

Riot components use custom tags which are nothing more than familiar HTML tags coupled with JavaScript. This eliminates the need to learn another templating language or syntax. For example: <todo> <h3>TODO</h3> <ul> <li each={ item, i in items }>{ item }</li> </ul> <form onsubmit={ handleSubmit }> <input> <button>Add #{ items.length + 1 }</button> </form> this.items = [] handleSubmit(e) { var input = e.target[0] this.items.push(input.value) input.value = '' } </todo> Riot tries to separate HTML and JavaScript, while still keeping them inside the component. This way, the HTML can also be neatly mixed with JavaScript expressions. See More

Top Pro

Supports server side rendering

Riot has support for server side rendering. The views and data are rendered on the server, then those views are sent as HTML to the browser when a user requests them. This helps with initial loading time and is very useful for SEO purposes because the web app is indexed by search engines same as other static websites that have their HTML on the server. See More

Top Pro

Easily pluggable with JS/HTML/CSS preprocessors

It is very easy to use your favorite preprocessors with the Riot compiler. Riot comes with CoffeeScript, ES6 (Babel), TypeScript, LiveScript and Jade support. You can also add your own parsers. See More

Top Pro

Very simple

It makes React look confusing as hell. Nothing against React - It's just that easy to implement! See More

Top Pro

Scoped CSS available in components

Riot supports scoped CSS inside components for every browser by rewriting stylesheet rules. See More

Top Pro

Lives well with any other library, framework and usage pattern

Since it's not opinionated, even the scripting can be in anything that can be transpired to JavaScript. See More

Top Pro

Separation of concerns with RiotControl

RiotControl is inspired by Facebook's Flux Architecture Pattern and it's a simple Central Event Controller/Dispatcher for Riot. It's extremely lightweight (like Riot itself) but unfortunately passes up on some features in favor of performance and simplicity. RiotControl helps with storing the stater of the application, by passing events from views to stores and vice-versa. Stores can communicate with many views and views can do the same with many stores, this enables to clearly separate concerns and inter-component communication. See More

Specs

Platforms:Android, iOS, Web, Linux, macOS, Windows, Electron

License:free open-source software

Search:yes

End-to-end encryption:yes

See All Specs

See All Experiences

128 46

score 337 · Answer 9

Bootstrap

Top Con

Large file size out of the box

Bootstrap has an out-of-the box filesize of ~276K, which is pretty large considering it's just CSS. Most of those styles aren't even used in 90% of web pages built with Bootstrap. By only including the required styles it can be trimmed by 70%-75%. See More

Top Pro

Consistency across browsers

The grid layout with the predefined CSS elements and JavaScript components make it easier to have consistency across different browser versions and even different devices. See More

Top Con

Too many classes

Bootstrap's over-reliance on HTML classes for styling can get very messy very quickly. There's also an overabundance of DOM elements which have a lot of classes and are more often than not nested inside DOM elements with even more classes. This gets problematic down the line because the maintainability of the project gets harder when the project starts to get large. See More

Top Pro

Responsive design philosophy

Bootstrap is developed to be instantly compatible with all sizes of screens, so you don't have to worry about which device the user is accessing your site from. Yet if you prefer, you can disable responsiveness of Bootstrap. See More

Top Con

Websites can start to look the same

If the initial Bootstrap colors and styles are not changed or edited, different websites start looking the same even if they have nothing to do with each other and they are made by different developers. See More

Top Pro

Well documented

Documentation is thorough, well organized and full of live examples and templates ready for use. Every component and every part of the framework is explained and covered in depth. See More

Top Con

Hard to customise

It's quite hard to customise Bootstrap using pre-processors like SASS and LESS, the only real flexibility is with typography and colours. See More

Top Pro

Custom builds

If you don't want to download the full Bootstrap framework. Custom builds of Bootstrap can be created, including only the desired CSS, CSS components, and JavaScript components. This can be done directly from the Bootstrap website by simply choosing what components to download. See More

Top Con

Large font sizes

Top Pro

Designed to get a site running quickly

Bootstrap is designed to get a site up and running quickly. Each of it's components is pre-configured to help with getting a site up and running quickly. See More

Top Pro

Great community

Bootstrap is very popular and has a large community. As a result of this it is much easier to find help with anything you might need. This also gives you a treasure trove of prebuilt components to use and add to your site. See More

Top Pro

Supports responsive embeds

Allows easily adding responsiveness to <iframe>, <embed>, and <object> elements. See More

Top Pro

Easily make professional looking websites

Bootstrap makes it easy to learn how to make professional looking websites. It can even make code junkies semi-enjoy design. See More

Top Pro

Customizable

Bootstrap can be customized in a variety of ways. Either by overriding the default CSS styles with new CSS styles or by editing the .scss Bootstrap files. See More

Top Pro

A wide variety of themes available

To help you avoid the "Bootstrap look", there are many resources that provide a great selection of themes and templates for Bootstrap. See More

Top Pro

One of the most popular ones

Ranked on GitHub as the most starred CSS repository. See More

Top Pro

Builders

Builders available, such as Pingendo and Layoutit. See More

See All Experiences

337 137

score 10 · Answer 10

CanJS

Top Pro

Great browser support

CanJS supports all modern browsers and IE9+. See More

Top Pro

CanJS can be used with any other library

CanJS is a collection of individual libraries, each separately available as npm packages. It's easy to use just what you need. See More

Top Pro

Real time support

CanJS's model layer (can-connect), support real-time updates to lists without adding any additional code. See More

10 0

score 9 · Answer 11

w2ui

Top Pro

Easy and clean API

Any component is well documented and have an easy API to access validation, dataloading and handling user events. See More

Top Pro

Lots of components/widgets

Library contains UI components like Datagrids, Forms, Tabs, SideBars, Toolbars and more. See More

Top Pro

Small library size

Only two files need to be included 1 .css and 1 .js, together they are only 365 kb. regarding to amount of components it is very small. See More

9 0

score 8 · Answer 12

Blocks.js

Top Pro

Small footprint

Blocks.js is just 16.5KB minified and gzipped. So it's pretty small. See More

Top Con

Relatively new

Blocks.js is a relatively new library. It doesn't have much support and there re not many people who use it. So if you run into any problems it would be hard to get solutions. See More

Top Pro

Modular structure

Apps developed with blocks.js are modular in structure and make use of reusable objects. This makes these applications very maintainable. See More

Specs

GZipped size:16.5K

8 0

score 91 · Answer 13

Mithril

Top Pro

Small, easy to learn API

Most other frameworks either offer a huge API to deal with model and view synchronization, or defer to other libraries & plugins to cater for relatively simple use cases. Mithril's API is tiny but complete. The natural reaction is to assume something is missing, but as you build you realise you incredibly fast, powerful and rich applications can be built using nothing but Mithril. See More

Top Con

Small API can make it unsuitable for larger more complex projects

Mithril's small API and small number of functions while helpful for small projects and applications where speed is needed, can add another layer of complexity in larger more complex applications where a more extensive API is needed out of the box. See More

Top Pro

Fast rendering

Mithril's loading times are very fast. This is because it's templates are compiled first and then served to the browser and because it uses a virtual DOM. The virtual DOM is a virtual tree containing all the nodes of the real DOM, every time anything changes in the virtual DOM, Mithril does not re-render the entire (real) DOM, instead it just searches and applies the differences. See More

Top Pro

No need to learn another syntax to write views

Most MVC frameworks use HTML templates to render their views. They are good and useful because they are easy to read and understand. But they add more complication to an app because it's practically a new language and syntax that needs to be learned. Mithril argues that separating markup from logic is just a separation of technologies and not concerns, so you can write Mithril views in JavaScript. Writing them in JavaScript also makes it easier to debug them (HTML templates can't be debugged). See More

Top Pro

Familiar to people used to MVC

Doesn't lock you into any complicated conventions or structures, only one function is required to create either a Controller or a View. You're free to implement your architecture exactly as you want, so you can focus on the purpose of MVC, making connections between computer data and stuff in the end user's head. See More

Top Pro

Small size

Weights just 8Kb gzipped and has no dependencies. A reactive stream module can be added for one extra Kb. See More

Top Pro

Great documentation

Mithril has a large and expansive documentation despite it's relatively small API. Mithril's GitHub repo has more documentation than actual source code. None of that documentation is auto-generated See More

Top Pro

Allows a smooth transition from other UI frameworks

One thing you need to start using Mithril is just a DOM node. With Mithril a developer is able to introduce the library step by step. See More

Top Pro

Allows you to choose which JavaScript libraries to integrate in your project

Mithril gives to the developer the flexibility to chose the best JavaScript library to use for a specific task. A huge framework like Angular instead forces you to use their API, which does not necessarily evolve as fast as the JavaScript ecosystem. Therefore you may end up in case when you are stuck using an API which is just not the best in terms of performance See More

Top Pro

Can be used without build systems

It's plain old JavaScript, can be used without webpack, gulp or grunt, just include it into your HTML and start writing your app. See More

Top Pro

Does not force you into a predefined structure

Mithril's API is pretty small compared to other frameworks. It forces developers to solve problems in JavaScript rather than in Mithril. Other frameworks with massive APIs force you to think in a way that suits the framework. Mithril doesn't do that. See More

Specs

GZipped size:8kb

See All Experiences

91 8

score 175 · Answer 14

Quasar Framework

Top Pro

Uses Vue.js 2.0

Vue 3.x available as a plugin. See More

Top Con

Developed by a single person

Statistically, apps being developed by a single person can be gone without warning. See More

Top Pro

Good documentation and coding samples

Top Pro

Massive suite of well test & optimized widgets

Instant rebuild for SPA, PWA, Cordova or Electron with Material/iOS Themes. See More

Top Pro

Designed from the outset for desktop & mobile

Top Pro

Can build/test your PWA with/without PWA wrapper

Top Pro

Supports server side rendering (SSR) like Nuxt + SSR/PWA

"Icon genie" builds app icons and splash images for platforms selected. See More

Top Pro

Ability to add custom server side code when using SSR

Specs

Platforms:Windows, Linux, Mac, Web

License:MIT

Mobile targets:Android, Blueberry, iOS, Windows Phone, Web

Supported languages:Javascript, Typescript

See All Experiences

175 13

score 2 · Answer 15

zUIx.js

Top Pro

Ease of use

Requires only basic HTML/Javascript knowledge. See More

Top Pro

In-browser bundler

Can pack assets and resources in the browser console with no need for any external tool. See More

Top Pro

Component-based

Creating a component is just a matter of creating 3 small files (html, css, js). Can share and load components across websites. See More

Top Pro

Web Starter Project

If you like Node.js and automatic build system, the zuix-web-starter is a "blank" web project featuring LESS, Markdown, Minify, Eslint checks, automatic bundling, PWA optimizations and much more. See More

Top Pro

Lazy-loading

Built-in lazy loading feature. Almost transparent. See More

Top Pro

Templates

With automatic fields mapping (data binding). See More

Top Pro

jQuery alike helper

Built-in DOM helper. Basically a lite subset of jQuery. See More

Top Pro

Examples

The zKit site is a collection of example components ready to use as-is or as a base for creating your own components. See More

See All Experiences

2 0

score 2 · Answer 16

Metayota HTML Engine

Top Pro

Fast and leightweight

The framework is only approx. 10 kilobytes in size and 2k lines of code. The custom tags can be lazy-loaded or preloaded. The rendering process is fast and selective, so only updated elements are rendered. See More

Top Pro

IDE for progamming

Metayota offers an IDE for programming or designing tags for this framework. There is no programming knowledge needed and all tags can be tested instantly. See More

Top Pro

Clean Code / Clean HTML

Readable, easy to maintain and clean code. The Metayota HTML Engine does not add any non-standard HTML elements to your code or any unintended tags or attributes. The HTML can be written, like it was intended by the designer. Only elements which are finished with rendering are added to the DOM (no flickering). See More

Specs

2 0

score 13 · Answer 17

Ractive.js

Top Pro

Supports a true templating language

Ractive fully supports a templating language. To be more precise, views are written with a variant of Mustache, which is also extended to support inline JavaScript expressions. Soon it will be able to support other templating languages. See More

Top Con

Ractive's two way binding can be a source of bugs

Two-way data-binding means that a HTML element in the view and an Ractive model are binded, and when one of them is changed so is the other. One-way data-binding for example does not change the model when the HTML element is changed. This is a rather controversial subject and many developers consider two-way data binding an anti-pattern and something that is useless in complex applications because it's very easy to create complex situations by using it and being unable to debug them easily or understand what's happening by just looking at the code. However, this is the default behaviour which can be changed to have one-way data binding. See More

Top Pro

Makes it possible to handle user interaction in a readable, declarative fashion

Ractive has a concept of proxy events, which translate a user action (e.g. a mouseclick) defined via an event directive into an intention (e.g. 'select this option'). This allows you to handle user interaction in a readable, declarative fashion. on-click='activate' with arguments: on-click = 'activate: {{a}}, {{b}}' It's activate (and not click, nor your function name) that is the name of the handler event that will be fired for any registered handlers created via ractive.on('activate', your_handler) ractive.on('activate', your_another_handler) Of course, Ractive also supports method calls like on-click='toggle(foo)' See More

Top Pro

Two-way binding configuration

Two-way binding can be turned off by those that are concerned it may be a source of bugs. See More

Top Pro

Step by step tutorial

They have a great interactive tutorial which makes the learning process easy peasy. You will get into it within a couple of minutes. See More

Top Pro

Virtual DOM

Instead of relying on the DOM, Ractive 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. See More

Specs

GZipped size:12K

See All Experiences

13 2

score 96 · Answer 18

React with pre-made components

Top Con

Large file size

React's react.min.js is 145.5KB in size. It's much larger than some other libraries that offer roughly the same features and it's almost the same size as some MV* frameworks such as Angular or Ember that offer more features out of the box. Although, it should be mentioned that sometimes having a smaller library may force developers to reinvent the wheel and write inefficient implementations on features that React already has. Ending up with a larger application that's harder to maintain and/or that has bad performance. See More

Top Pro

Easy to reuse components

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. See More

Top Con

You have to learn a new syntax

Requires to learn a custom syntax, JSX that has some gotchas and introduce complexity, a steeper learning curve, and incompatibility with other tools. Though you can opt out from JSX and use vanilla JS instead. But that is not recommended since it adds a lot of unneeded complexity which JSX tries to avoid. See More

Top Pro

Supported by Facebook and Instagram

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. See More

Top Con

Dependency hell

With all the third party components available for React, which when used smart is a good thing, can result in huge code bloat when used dumb. Javascript sizes can go from KB to MB without doing too much though. See More

Top Pro

Flux architecture pattern

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. See More

Top Con

No support for legacy browsers

React has recently dropped support for Internet Explorer 8. While the library may still work on IE8, issues that affect only IE8 will not be prioritized and/or solved. See More

Top Pro

Virtual DOM support

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. See More

Top Con

Slow VirtualDOM

React's VirtualDOM is relatively slow compared to other libraries that implement a VDOM. See More

Top Pro

Easy to write tests

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

Top Con

Verbose

React gets a little verbose as applications get more complicated with more components. It's simply not as straightforward as simply writing HTML and JavaScript would be. See More

Top Pro

Tested on Facebook itself

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. See More

Top Pro

Can be used with different libraries

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. See More

Top Pro

One-way data flow

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. See More

Top Pro

Extensive SVG support

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

Top Pro

Template engine independent

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

Top Pro

Good debugging tools

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. See More

Top Pro

Server side rendering

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. See More

See All Experiences

96 13

score 28 · Answer 19

Kendo UI

Top Con

Expensive commercial tools [$699, $1,499]

The other core tools developed with Kendo are the commercial tools. There is the Professional version for $699 that will result in more jQuery UI widgets and client support. The $1499 "DevCraft" Complete edition gets developers the DevCraft .NET toolbox, testing and debugging frameworks and applications, as well as priority support. See More

Top Pro

Free Core tools

Kendo UI is separated into a commercial and open source frameworks. The core of Kendo UI is in the open source frameworks, but some usability and benefits of Kendo UI are lost without the commercial version. See More

Top Pro

Platform-based UI

Kendo knows what device it is being viewed on so it can adjust the UI accordingly. If a user is on a PC the user will see things differently than on a mobile device. Between iOS and Android the user will also notice a different as it pulls from the core UI of those core systems. See More

Top Pro

Theme Builder

An interactive tool that has been created to customize an apps theme. Users are able to select from many pre-defined themes, edit them, and download the theme to bring into a project. See More

28 5

score 28 · Answer 20

Angular

Top Pro

Great tooling and language support

Very good CLI and webpack, bundling, testing, deployment support. Deep TypeScript integration and support. See More

Top Con

Slightly over-engineered

Very enterprisey - made for huge architectures and with tons of declarative, non-intuitive annotations it makes it overkill for very small projects. See More

Top Con

Native i18n support over-engineered

Not developer-friendly. Switching languages need reloading the whole page. There are third party solutions that work better. See More

28 5