A Brief History of client-side JS: Why React is Awesome | Prezi

var hiddenBox = $( "#banner-message" );

$( "#button-container button" ).on( "click", function( event ) {

hiddenBox.show();

});

• Auto-synced models via REST API

• Compatible well with other libraries

• Robust event system

• Documentation

<div class="some-class" id="some-id">

<button class="click-me">

Click Me!

</button>

</div>

• Cross-browser API

• Powerful DOM Manipulation

• Painless Ajax

• Components, not templates

• Business Logic and UI in the same context

• Encourage High Cohesion & Loose Coupling

• Abstraction, Composition, Expressivity

• Reusable, Composable, Unit Testable

• Components store data using State & Props

• JSX views

• State is only used in root components

• Props are passed from parent to child components

• Props are immutable

• State is mutable

• Minimal (only UI layer)

• Immutable data across views

• No data-binding whatsoever

• Compatible with other libraries

• Virtual DOM provides fastest view rendering (60fps) due to idempotent DOM manipulations

• Documentation

• Backed by Facebook

• Bare-bones features

• Lots of Boilerplate

• Views suck (jQuery style)

• DOM Manipulation is slow

• Tight Coupling with HTML tags leads to scattered spaghetti code

• Extremely difficult to track DOM event handlers

• Re-establishes best practices

• Change of mindset

• True MVC pattern with Rails-like magic

• Handlebars' robust templating system

• Backed by Rails community

• Two-way Data Binding

• Declarative HTML

• Backed by Google

• Too much magic behind the scenes make it harder to learn

• Lots of context switching

• Two-way data binding much more complicated

• Documentation

• Directives are hard

• Dirty Checking is slow

• Redefining well-established terminology

• Logic all over the place