What is the best alternative to zUIx.js?

Question

Built By the Slant team

Find the best product instantly.

4.7 star rating

Try it now - it's free

score 19 · Answer 1

Inferno

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

Pretty light-weight

Inferno weighs in at 9kb gzipped, which is light-weight. 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

Fast performance

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

Top Pro

React compatability

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

19 1

score 91 · Answer 2

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 2 · Answer 3

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 28 · Answer 4

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

score 10 · Answer 5

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 6

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 77 · Answer 7

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

77 14

score 26 · Answer 8

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 101 · Answer 9

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 (Safari):13K

v2.0 GZipped size (Chrome):10K

v1.0 GZipped size:53K

v2.0 GZipped size (Edge):36K

See All Specs

See All Experiences

101 22

score 70 · Answer 10

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

70 20

score 29 · Answer 11

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 520 · Answer 12

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 128 · Answer 13

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

Elm

Top Pro

No run-time exceptions

Lack of run-time exceptions makes it easy to produce large swathes of reliable front-end code without drowning in tests. See More

Top Con

Lack of typeclasses

Elm doesn't have typeclasses which means some code needs to be duplicated. A fix in a function that needs typeclasses means all of the duplicates need to be fixed too. See More

Top Pro

Inferred static typing

ML static typing is great because it's always there, you just choose how explicit you want to be and how much you want the compiler to do. See More

Top Con

limited js interop

only one way ports are available as a crude js FFI. This means you can only call functions both directions but will not get a result. See More

Top Pro

Super easy refactoring with very helpful compiler errors

In no other language you can refactor so easy without any worries, since the compiler will guide you through. It is like TDD but than compiler-error driven. See More

Top Con

Harder to get buy-in from devs and mgmt

It's a total divergence from what most people are used to in the JS ecosystem. The change in syntax can be scary, the change in approaching problems can be scary. The fact that it's not backed by FANG can be scary. The fact that it's not v1.0 can be scary. The governance model and the deliberately slow release cadence can be scary. There are a couple harsh medium articles, hackernews/reddit posts out there made by people with an ax to grind that can be scary if you don't have a better picture of the Elm community, the tradeoffs that have been made, or the benefits to be had over other options. None of these are good reasons to write off further investigation of a great tech, but it happens. See More

Top Pro

Designed around high-level front-end development

As Elm was designed as a front-end langauge, it has out of the box support for things like DOM-element creation, letting programmers focus on their application logic, rather than implementation details specific to the web. See More

Top Con

Code Repetition

Because of the lack of genericness Elm needs a lot of code to be repeated. There are 130+ implementations of map in elms core libraries. See More

Top Pro

Great and simple way to learn Purely Functional Programming

You can try to apply some functional programming ideas in other languages that have an imperative basis, but you haven't seen the real power unless you tried it in the environment of purely functional programming. Elm is a simple language with great learning resources and easy graphical output, which makes it easy to explore the power of functional programming. Plus programming in Elm is very readable. See More

Top Con

Features get removed without warning

Often features that are deemed to be misused by the community like infix operators get removed without much of a warning. See More

Top Pro

Good tooling

All major editors have great support. With Atom for example, Elm plugins are available for linting, formatting, make/compiler support and Elmjutsu will simply overflow you with super useful functions, like navigate to referenced definition and show expression type. See More

Top Con

Community harsh if criticised

If one even dares to start a discussion about a feature on elms slack, discord, subreddit or github one will be aggressively shut down often argueing that one should use purescript instead See More

Top Pro

Batteries included

The Elm Architecture means you don't need to spend valuable time and effort choosing the right frameworks, state management libraries, or build tooling. It's all built in. See More

Top Con

Poor Windows support

Few if any of Elm's core contributors are Windows users and breaking bugs are sometimes left for weeks or months. See More

Top Pro

Static module system

Elm uses easy to use modules. Use: import List import List as L import List exposing (..) import List exposing ( map, foldl ) import Maybe exposing ( Maybe ) import Maybe exposing ( Maybe(..) ) import Maybe exposing ( Maybe(Just) ) Creation: module MyModule exposing (foo, bar) See More

Top Con

Good for beginners not good for experts

Development in elm is quite nice until you need some more advanced features. These however are actively discontinued and removed because elm wants to establish a "single way of doing things" philosophy See More

Top Pro

Missing syntactic sugar

Easy to learn, most functions have only one way, not 5 alternatives where you must study where to best use what. See More

Top Con

Updates break existing code often

The last few updates of elm broke existing code in major ways. See More

Top Pro

Growing community

Top Con

Adds an additional layer of abstraction

Some users claim that Elm adds an additional layer of abstraction, meaning that it is one more hurdle between the brain and the product. See More

Top Pro

Interactive Programming and Hot Swapping

Support for hot swapping and interactive programming is included. See More

Top Con

Functional programming itself has quite a steep learning curve

Functional programming can be quite difficult to get your head around. It takes time to unlearn object orientational habits. See More

Top Pro

Easy to code review

The lack of side-effects and simple, consistent language semantics make it easy to quickly review incoming changes. See More

Top Con

No Genericness in the future

Currently there is no code genericness like typeclasses possible, it has been officially stated that this will never change. See More

Top Pro

Higher confidence in code correctness and quality

Pure functions, immutable data structures, amazing compiler, clean and homologous syntax used for HTML, logic, and optionally to replace CSS, elimination of entire classes of bugs so you don't even need most unit tests. These factors lead to better code, better programs, higher confidence, and ultimately, more satisfaction. See More

Top Con

Not database-friendly

It is lots of work to make a server or database your "one source of truth", as Elm makes you write endless JSON parse boilerplate to talk to the server. See More

Top Pro

Not quite Haskell semantics

Luckily you do not have to learn Haskell to be able to do any Elm. It is meant to be a language that compiles to Javascript, so for Javascript programmers (Front end) not for CS students who want to learn as many different algorithms as possible. See More

Top Con

No Syntactic Sugar

Often you need to write longer and less readable code because there are no alternatives that are more concise. See More

Specs

Platforms:Windows Linux Mac Web

Current stable version:0.19.1

GZipped size:23.2 kB

See All Experiences

479 170

score 3 · Answer 15

Ractive

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

Top Pro

Live, reactive templating

Ractive.js is a template-driven UI library, but unlike other tools that generate inert HTML, it transforms your templates into blueprints for apps that are interactive by default. See More

Top Pro

Powerful and extensible

Two-way binding, animations, SVG support and more are provided out-of-the-box – but you can add whatever functionality you need by downloading and creating plugins. See More

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

3 3