Towards Universal JavaScript
summary
Claims that same JavaScript can run on server and client to fix SEO and performance tradeoffs, with concrete workarounds and costs: RedMart replaces headless-phantomJS reverse-proxy caching by server-side rendering using React + Node + Express, bundling with Webpack and Babel, hydrating DOM via renderToString and serializing state to dehydrate/rehydrate a Redux store. Demonstrations show it works but exposes real problems: coordinating multiple API fetches (use isomorphic-fetch), DOM mismatches, cookie/session differences, and extra infrastructure and maintenance.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:36What is Universal JavaScript ?
- 3:13Why Universal JavaScript ?
- 3:32Performance Maintainability
- 9:59How to build a Universal JavaScript app?
- 27:28Not really!
related talks
24mUniversal Applications
30mThe Bumpy Road to Universal JavaScript
44mServer Side Rendering from the trenches
28mJavaScript SEO (The "Right" Way)
45mBuilding Isomorphic Apps (Updated)
31mThe Bumpy Road to Universal JavaScript
10mUniversal Apps: Architecture for the Modern Web
43mIsomorphic JavaScript apps
