Ranked in these QuestionsQuestion Ranking

Pros

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 viaractive.on('activate', your_handler)ractive.on('activate', your_another_handler)

Of course, Ractive also supports method calls like on-click='toggle(foo)'

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.

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.

Cons

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.