What is the best alternative to Marko Widgets?

Question

Built By the Slant team

Find the best product instantly.

Lustre recommends the best products at their lowest prices – right on Amazon.

4.7 star rating

Add to Chrome

Try it now - it's free

score 9 · Answer 1

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

9 2

score 34 · Answer 2

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

Awesome responsive material skins

Great design and icons pack. 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

Mature project

Regular updates and releases. See More

Specs

Site:webix.com

See All Experiences

34 2

score 120 · Answer 3

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

120 39

score 8 · Answer 4

w2ui

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

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

8 0

score 7 · Answer 5

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

7 0

score 88 · Answer 6

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

v2.0 GZipped size (Edge):36K

v2.0 GZipped size (Safari):13K

v2.0 GZipped size (Chrome):10K

v2.0 GZipped size (Firefox):32K

See All Specs

See All Experiences

88 22

score 461 · Answer 7

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

Very enterpris-ey in design and tooling

Top Pro

Single file component

Very useful. See More

Top Con

Poor typescript support

Very basic typescript support. See More

Top Pro

Lightweight

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

Top Pro

Vuex store, events system

Top Pro

CLI and Webpack integration

Top Pro

Reactivity system

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

461 115

score 16 · Answer 8

Inferno

Top Pro

Pretty light-weight

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

Top Con

Some React components may not work with Inferno

Inferno and React have different public and private APIs. If 3rd party components use a private API then it's almost certainly going to break when you use it with Inferno. Once React Fiber is implemented, even libraries that are currently working will break and will not be supported by Inferno. See More

Top Pro

Fast performance

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

Top Con

Not very popular

Which can hinder one's opinion of its future, but the future of all "frameworks" is to break things into smaller pieces, so inferno very well might get used by the big names in the future. See More

Top Pro

Modular

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

Top Pro

React compatability

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

16 1

score 61 · Answer 9

Knockout

Top Pro

Easy data binding

Knockout uses HTML5 data attributes to bind HTML elements to data objects in javascript. This allows more work to be done by the framework rather than requiring you to specify where data should be bound in the javascript. The data binding is very intuitive as the bindings are done within the HTML itself in the location it should be bound. See More

Top Con

Slower than others when amount of objects grows

Knockout has a bad performance when the dealing with large amount of objects. You can see more here. See More

Top Pro

Easy to learn

Has a low entry barrier and an easy learning curve. It's especially easy to learn for beginners. See More

Top Con

Can become complex once the application grows large

Knockout leaves the application structure to the developer and it can become quite complex and unmanageable in the hands of a beginner once the application grows large and complex. See More

Top Pro

Built in templating

Bindings in Knockout can also be used to control the generated structure of the HTML. There are bindings provided to allow for iteration and conditionals. The structure of the html reflects the structure of the data so iterative elements are bound to arrays in the data model. Having the HTML structure maintained by bindings keeps the templating simple, easy to read, and maintain. Knockout also allows for string based templating so you can use whatever templating library you prefer. See More

Top Con

Two way binding requires a little extra work

When allowing users to edit existing data, the two-way binding of observables means you'll need to have to save original values before they're edited, to make comparisons or revert if the user cancels the action. See More

Top Pro

Legacy browser support

Supports a large number of browsers, including IE6. See More

Top Pro

Great documentation

The excellent tutorials with built-in exercises are a great learning experience, even for people without prior MVVM and data binding experience. See More

Top Pro

Lightweight and plays nicely with other libraries

Top Pro

Dynamic models help with keeping the code simple and clean

Models in Knockout can be watched to keep the page data up to date by using observable objects. The observables notify Knockout when data is changed and automatically updates the page when this happens. By having Knockout maintain this relation, it keeps the front end code cleaner and simpler, and by enforcing a consistent pattern with observables the methodology can be more robust. See More

Top Pro

Very flexible

One can do a lot of things and it keeps self references and other types of loops under control. See More

Top Pro

It's only a library

Knockout does one thing, and does it well. It doesn't try to take on more than one area. It does MVVM data binding and that is it. See More

Top Pro

Simple manageable modules

Using components is a great way of breaking up large modules into simpler ones. See More

See All Experiences

61 12

score 183 · Answer 10

Aurelia

Top Pro

Out of the box Typescript support

Full support for Typescript built in 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

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

No big success stories yet

There are no notable big web products build with aurelia yet 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

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

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

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

183 29

score 19 · Answer 11

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

Awesome CLI

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

Top Pro

Lots of examples and libraries

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

Specs

Site:https://preactjs.com

Current stable version:8.1.0

GZipped size:3.3kb

19 6

score 210 · Answer 12

React

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

Heavy on memory

React's virtual DOM is fast, but it requires storing elements in the virtual and real DOM increasing memory usage for the page. This can be a real problem for single-page webapps designed to be left running in the background. 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

Top Con

Template(view) mixed into code

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

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

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 Con

You have to learn a new syntax

Requires learning 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

Not a complete solution

React does not do everything for the developer, it's merely a tool for building the UI of a web app. It does not have support for routing or models, at least not out of the box. While some missing features can be added through libraries, to start using React and use it in production, you still would need to have experience, or at least a good grasp on what the best libraries to use would be. 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 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

Template engine independent

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

Top Con

Renders too frequently

Top Pro

Functional programming style leads to less buggy UIs

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

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 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

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 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

Keep control over your app's logic

React is just a view library, so you still have (almost) full control over how your app behaves. See More

Top Pro

Supported by ClojureScript libraries

Reagent, Om, Rum, etc. 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 millions of people experiencing it every day. See More

Specs

GZipped size:45K

See All Experiences

210 95

score 10 · Answer 13

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 80 · Answer 14

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

80 8

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

RC HTML RENDER

Top Pro

IDE for progamming

RC 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

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

Clean Code / Clean HTML

Readable, easy to maintain and clean code. JJRE 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 12 · 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

12 2

score 25 · Answer 18

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

25 4

score 16 · Answer 19

Amber

Top Pro

Includes an IDE

Amber includes an integrated development environment with a class browser, workspace, transcript, object inspector and debugger. See More

Top Con

Very few learning resources

There are very little learning resources for Amber outside the official documentation. Which may not be enough for beginners, especially people that don't have much experience in programming. See More

Top Pro

Smalltalk is a simple, elegant, and powerful language

Top Pro

One-to-one JS equivalent

Amber is written in itself, including the parser and compiler, and compiles into efficient JavaScript, mapping one-to-one with the JS equivalent. See More

Specs

Platforms:Windows Linux FreeBSD

16 4

score 68 · Answer 20

Backbone

Top Con

Requires more coding compared to other frameworks

Because many features are not provided out of the box, you either have to write more base class code to get those features, or find a plugin that provides them in a way you like. It does not provide much structure either, things like memory management must be kept in mind by the developer, also the lack of view lifecycle management makes state changes prone to memory leaks. See More

Top Pro

Gives you the freedom to implement views however you want

A lightweight view class is provided but there is no default templating method implemented. Because views are minimal it allows for much more freedom to implement views however you would like, and because of this freedom it's possible to write views to more uniquely adapt to a problem. User interactions are done within an events object that allows these interactions to be segregated from the rest of the view code which makes the behavioral aspect of the view easier to read and manage. See More

Top Con

Can easily lead you to spaghetti code

Heavy event-binding can lead to unmanageable spaghetti mess. BB tempts users to overuse it for no reason. See More

Top Pro

Can be combined with any library you want

Backbone can be combined with any library of your choosing, giving you the ultimate flexibility in creating customized solutions for unique projects. Even the only two backbone requirements, jQuery and underscore can be replaced with equivalent libraries like zepto or lo-dash. See More

Top Con

No data binding

Backbone does not have data binding support. However, there are some libraries that can be implemented in order to have data binding in Backbone. Such as Epoxy See More

Top Pro

Large community

Backbone has existed longer than most frameworks, and has a large following of users and projects using it as a framework. See More

Top Pro

You can call underscore.js methods directly on Backbone objects

Backbone collections and models are extended by underscore.js method allowing you to call underscore methods directly on the Backbone objects. See More

Top Pro

Easy to interface with the API

Backbone provides Model and Collection classes that provide strong analogs to restful resources. These strong analogs allow you to interface more naturally with the API, and makes it easier to write custom behaviors for more complicated API interactions. Collections provide a variety of powerful manipulation methods that are integrated from the underscore library, that allow you to manipulate, sort, and filter collection data easily. See More

Top Pro

Easy to implement complex user interaction

Because all the state is managed by Models and Controllers, and they are extendable objects, you can isolate all the state logic onto those objects allowing the rest of the application to not worry about it. The app is simplified to just taking in input to modify the Models and Controllers, and updating the views to reflect them, but none of the state needs to be a concern outside of the Model and Controller classes. See More

Top Pro

Doesn’t force you into a particular coding style or paradigm

There is no “magic” happening below the surface: the source code is clear, readable and well commented. Backbone is also “lightweight” in the sense that it doesn’t require a ton of buy-in to use. It can be easily integrated into an existing page, and you can choose to only use certain components of the library (Views without Models or Collections, for example). While there are many frameworks that seem to be faster to get started with, Backbone’s lack of surprises, clear documentation, speed & flexibility make it a good fit for all types of apps. See More

Top Pro

Extendable with plugins

Because Backbone is so simple, and the different components are very well isolated, it is very easy to extend the functionality of Backbone. If you're writing your own extended code it's easy to keep it separated out, and share with the community. The community also has many plugins already available, which you can pick and choose to use to fit your programming style. See More

Top Pro

Easy to abstract interaction

All Backbone classes extend an events class that allows for listening and triggering functionality. Because all classes implement events by default it is easier to provide asynchronous communication between objects, and it allows better abstraction of interaction so the event emitting object does not need to know the structure or existence of the receiving object. See More

See All Experiences

68 20