Client Side Frameworks Suck and Why that doesn't matter
summary
Argument: many client side frameworks overpromise yet still solve real problems. The concrete claim is that Sammy.js is a small Sinatra inspired router that focuses on Sinatra-inspired routing and client-side templating rather than forcing data models. Examples: Sammy powers a Paperless Post design tool, driving URL state and async template rendering for prototypes. Result: it ships and speeds prototyping but does not scale to complex data modeling or replace a full MVC stack.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:30Framework Myths
- 6:50Smaller is better
- 10:05Myth of the one true way
- 13:05Fashion statements
- 15:45Fame and fortune
- 17:25Whats good for you
- 19:31Samia
- 21:00Template munging
- 25:44The truth of work
related talks
01h 29mClient-Side UI Smackdown
32mWhy everybody needs to use a framework
29mThe Front-end Takeover
34mYour Front End Framework is Overkill - Server Side Javascript w/ Rails
38mThe Front-End Future
45mNo framework frontends in practice - use the platform!
48mClientside templates for reactive UI
36mRails Vs. The Client Side