React
– Server-side renderable
– Components work on the fronted and backend
React
– Just compares about state components
– Redux lets you go back and forward in time via a JSON blob
#WCAVL
React:
– Components
– JSX (which looks like butchered HTML)
– The hardest to explain because it doesn’t do anything for you
React:
– New “cool kid”
– 26KB but doesn’t come with much
– Just the view layer *V*
– “Give me data, I’ll put it on a page for you”
Ember
– Handlebars includes if and else statements
– Rest of logic goes in your controller
Ember:
– Supports virtual DOM & Components
– Claims better performance than React but that’s crap
@harpreetsb More coming.
Ember:
– Ember data is like GraphQL for the Ember ecosystem
– Jargony gobblidgook
Ember:
– CLI use is highly recommended
– Other frameworks use NPM
– Need to buy in to the Ember ecosystem
– Kind of like RoR
Ember:
– Built by same team being jQuery and Ruby on Rails
– 136.2KB (jQuery + Handlebars)
Angular:
– 4 different write ways to do anything
– You’re writing things the way you want them
– Easy to make spaghetti code
Angular:
– Lots of built-in functions and filters (currency etc.)
– Community is massive
– Performance is “so-so”
#WCAVL
Angular:
– 39.5KB
– Create custom DOM elements/components
– Logic is mixed in with HTML: ‘ng-*’ stuff
Angular 2 is totally different than Angular 1
Angular 1.x vs Angular 2.x? “Angular 2.x is crap”
Backbone:
– No 2-way data binding
– Asks you to tell it when to be updated
– Performance can be an issue
– WP Media Library
Backbone:
– Not opinionated
– Very flexible
– If you don’t take advantage of models there is really no point in using it
Backbone:
– Models
– Views
– Collections
No real Controller layer for logic.
#WCAVL
BackboneJS is included with WordPress.
– Really tiny. Amazing for how much it does.
– 43.5KB with underscore and jQuery dependencies
#WCAVL
Learning JS frameworks is hard. They’re all pretty different.