Sam Skjonsberg - SeattleJS Conference 2017

on YouTube ↗11m

" summary

Built an isomorphic React SPA to power Semantic Scholar but initial client-side rendering prevents Google from indexing content, forcing server-side rendering to recover organic traffic. Bundle growth pushes load times to 20 seconds on 2G and requires dynamic chunking and smarter initial-data selection because serializing the full store balloons HTML. Isomorphism introduces platform-branching complexity (cookies, HTTP headers) and more tests. Perks include perceived speed, code reuse and developer happiness, but analytics need custom instrumentation and extra test coverage.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 1:08What We Built
3. 2:25Test Coverage
4. 2:49Code Reuse
5. 6:20Isomorphism Is Hard
6. 7:09Traditional Server Rendered Application
7. 9:32Conclusion

" related talks

• 45mSPA, isomorphic and back to the server: our journey with JSAlessandro Nadalin · jsDay 2017
• 38mBuilding Isomorphic Web Applications with ReactElyse Kolker Gordon · Strange Loop 2015
• 45mBuilding Isomorphic Apps (Updated)Spike Brehm · JSConf.Asia 2014
• 44mRethinking Isomorphic JavaScript with SolidStartRyan K Carniato · TheJam.dev 2023
• 28mSingle Page Applications - was it a good idea?Mateusz Ostafil · 4Developers 2022 Online
• 44mServer Side Rendering from the trenchesWilliam Durand · jsDay 2018
• 31mReact Server-Side Rendering | Isomorphic JavaScriptRuben Sargsyan · JavaScript Conference Armenia 2018
• 39mTowards Universal JavaScriptSarmad Sangi · JSConf.Asia 2015