Use Cases For Javascript Frameworks
summary
Compares concrete tradeoffs: jQuery for small DOM tasks and legacy plugins, underscore/lodash for functional utilities, Backbone (often with Marionette) when models/collections must organize complex client data and to integrate with WordPress media components, Angular for faster, full-featured single‑page apps with built‑in services and bindings, and React as a component‑based view layer paired with Flux/Redux for single‑source app state and better performance via a virtual/ shadow DOM. Recommends matching tool to scale and WordPress constraints.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:18let library, framework
- 3:00Library: Pre-written code you can include and use in your app or project
- 3:10Framework: Design decisions for your code that include libraries
- 3:50Breaking Down Use Cases
- 5:52Why We Start w jQuery
- 6:51jQuery Today
- 8:55Rethinking What We Need
- 9:12Functional Utility Libraries
- 10:30Underscore & Lo-Dash
- 14:22Code Organization
- 17:53MVC MV
- 18:46Backbone Angular React
- 20:54Models & Collections Views Small Least opinionated Little verbose Low learning curve
- 22:39Backbone & Marionette
- 22:52Better views Auto handles rendering Shadow DOMS Abstracts controllers Ships with Radio
- 26:22Largest Easy to start Models & Collections Bindings Factories & Services It's a Framework
- 28:44Just the view Component based State and props Component lifecycle Shadow DOM Great performance Not a framework
- 31:26Flux & Redux
- 32:04What Didi Choose? :
- 34:29JavaScript
