Ractive JS
Ractive JS
Top 43%348 points
Top 43%
Key features and highlights

Ractive JS: 20 facts and highlights

1. Has two-way databinding

Models and views can be bound to update each other.
Ractive JS
53% have it

2. minified file size without dependencies

Smaller file size means faster load times.
65KB
Flight: 14KB

3. Supports routing and deep linking

Routing allows interaction with the browser url. This is very important for a good user experience if you are building one-page apps.
Ractive JS
67% have it

4. Uses a templating engine

Template engines allow for easy and flexible UI building.
Ractive JS
67% have it

5. Supports one-way data binding

Views can be bound to update automatically when an observable object changes.
Ractive JS
80% have it

6. Is DOM manipulation library agnostic

Does not require or seriously encourage the use of a specific library (like jQuery, Zepto or MooTools) to handle DOM manipulation and can be used with one the developer prefers.
Ractive JS
20% have it

7. Published under MIT License

The MIT License is a very permissive license which allows all uses, including business use, without warranty.
Ractive JS
87% have it

8. dependencies

Less dependencies means less extra scripts to include, usually resulting in less development overhead and faster load times.
0
SproutCore: 0

9. Supports composed (partial) views

Allows for nesting view templates into top-level views from within a template.
Ractive JS
60% have it

10. minified file size including dependencies

Smaller file size means faster load times.
65KB
Maria: 20KB

11. Updates the DOM asynchronously

Model changes do not immediately result in view updates but are queued and dispatched as a group. This can be a lot more performant than instant view updates.
Ractive JS
27% have it

12. Integrates well with third party libraries to enable Promises/A+ support

Allows the use of libraries like jQuery Deferred to support promises. Promises are a popular alternative to callbacks when dealing with server responses.
Ractive JS
33% have it

13. Uses observables for data binding

Models are observed for changes. This is a well known pattern. Can be more performant than dirty-checking in some cases.
Ractive JS
80% have it

14. Has an official, up-to-date entry in the npm package manager

The node package manager can also be used for managing front end scripts.
Ractive JS
47% have it

15. number of years old

Older frameworks are often more stable, battle-proven and there are more resources and tutorials on them. As a company you have a larger talent pool to recruit from.
0years
Sammy JS: 4years

16. Officially supports Bower dependency management

Bower is an easy-to-use, npm-like package manager for frontend applications.
Ractive JS
53% have it

17. Maintains an internal DOM copy

This avoids constant re-rendering of all elements by comparing the mock DOM with the actual DOM and only rendering the changes.
Ractive JS
7% have it

18. Works with AMD libraries such as require.js

Asynchronous Module Definition libraries allow for easy modular, clean programming. If a framework does not work well with such libraries, it might have some other means to modularize its components and resolve dependencies, like Dependency Injection.
Ractive JS
60% have it

19. versions of Internet Explorer supported

Legacy browser support can be important for corporate projects and projects with a large user base consisting of Internet Explorer users.
7
rAppid JS: 0

20. Supports animation

Includes facilities to easily create view animations.
Ractive JS
7% have it

Top 10 MV* frameworks

Add to comparison
    Compare
    This page is currently only available in English.