Pivoting to React, at Scale

Pivoting to React, at Scale

JSConf via YouTube Direct link

Intro

1 of 27

1 of 27

Intro

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Pivoting to React, at Scale

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Always be pivoting The last 20% of a rewrite takes 80% of your time
  3. 3 Meet Denzel, 2013 web platform Built on Backbone.js and Django
  4. 4 Problems with Denzel Performance bottlenecks, CSS/JS bloat, dual code paths
  5. 5 And more ES6, NodeJS, Babel, Webpack
  6. 6 Defining "at scale"
  7. 7 498, 151 lines of code just in our web app! 164 web developers
  8. 8 Pivoting smarter What data structure is a web application most like?
  9. 9 It's a tree
  10. 10 Top down vs. bottom up
  11. 11 Things we did right
  12. 12 Measuring individual features
  13. 13 Backbone lite 80% of the functionality, none of the dependencies
  14. 14 Declarative states
  15. 15 Scaling communications
  16. 16 Mistakes were made
  17. 17 Suggested learning order: React, ES6, npm, JS bundlers, routing. Flux Redux
  18. 18 No top-down strategy
  19. 19 Keeping HTML structure
  20. 20 Data flow
  21. 21 Coupling fetching data and rendering
  22. 22 Testing
  23. 23 The true value of React Testability, not speed
  24. 24 CSS strategy Or lack thereof
  25. 25 Conclusions
  26. 26 Iteratively update semantics To ease the pain of pivoting your JS framework
  27. 27 DNA == code (This expression would fail a strict equality check)

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.