Pitfalls and Opportunities of Single Page Applications

on YouTube ↗33m

" summary

Covers concrete tradeoffs: uses Backbone and a tiny simple-history.js demo to show pushState over hashbang with working back/forward and no hash fallbacks, demoing continuous audio playback and client routing; recommends server-side rendering and code reuse (Node.js) to fix slow first loads — example code on GitHub — and notes Twitter dropped hashbangs; describes pragmatic error handling and aggregation using global onerror plus services like Airbrake/Bugsense for thousands of client errors, and sharesable templates via server-side rendering with shared Node.js code.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 4:27Opportunities
3. 5:53Pitfalls
4. 7:06Single Page
5. 9:16HTML5 history API
6. 10:31HTML5 history libraries
7. 17:03Server side rendering
8. 22:06Error handling
9. 22:22Error types
10. 24:52Aggregation options
11. 26:52Worth the trouble?

" related talks

• 51mBuilding Amazing Single Page Applications the Right WayJustin Meyer · GOTO Chicago 2015
• 24mBuilding Realtime Singlepage AppsHenrik Joreteg · NodeConf 2011
• 38mThe Front-End FutureFrancis Hwang · GoRuCo 2012
• 40mClient Side MVC and The Gosh Darn Back ButtonHarry Brundage · Spotlight: Advanced JS 2013
• 38mEmbrace the frontend revolutionÁlvaro Sánchez-Mariscal · Codemotion Roma 2014
• 18mThe need for speed - Single-page apps, Optimistic UIs, ReactivityGuillermo Rauch · dotJS 2013
• 30mJust another ECMAScript Trait Syntax ProposalStop breaking the web and start building server-rendered web apps using next.jsHenrik Wenz · JSUnconf 2017
• 32mWhy you don’t need a Single Page AppFlorian Krause · code.talks 2022