A model walks into a JavaScript framework

on YouTube ↗04m

" summary

Argues that squeezing front-end code into strict MVC/NVC is causing bad JavaScript designs and deep callback nesting that raises runtime exceptions; recommends borrowing battle‑tested patterns from Cocoa/Objective‑C, specifically delegation, to move responsibilities off controllers and better handle evented, asynchronous UI code; compares front-end needs to backend habits and points out that current popular JavaScript MVC frameworks lack those complementary patterns; offers no finished demo but promises to try these patterns to reduce callback hell in future work.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 0:24JavaScript MVC frameworks
3. 1:05Comfort Zone
4. 1:40Functions as First Class Citizens
5. 3:15Patterns that are complementary to MVC

" related talks

• 34mWe need to talk about the front webAngela Ricci · ffconf 2023
• 18mA framework author's case against frameworksAdrian Holovaty · dotJS 2017
• 44mModern JavaScript: Moving Beyond jQueryDerek Binkley · Dutch PHP Conference 2018
• 25mModern JavaScriptRebecca Murphey · JSConf US 2011
• 49mFrom Frameworks to SuperframeworksSergey Yuferev · HolyJS 2017 Piter
• 22mThe vanilla wayGuido D'Orsi · jsDay 2018
• 50mI Don’t Care About Your JavaScript FrameworkNéstor Salceda, Dani Latorre · Software Craftsmanship Barcelona 2017
• 01h 29mClient-Side UI SmackdownCraig Walls · SpringOne2GX 2012