Throwing Out ReactJS
summary
Describes how Kasta removed ReactJS from a large site to avoid long-term JavaScript composition conflicts like those experienced with jQuery. Explains the problems of excessive JavaScript and library-composition conflicts on big projects, and presents the alternative approach and results Kasta adopted after dropping React.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:19JS frameworks before React
- 14:57React problems and alternatives
- 24:34Finding React alternatives
- 33:48Twin Spark framework
- 40:35Transition results and performance
- 52:22Intercooler vs LiveView
- 1:02:51Q&A
- 1:17:12Summary
related talks
36mKeep it simple! How to apply KISS principle in modern frontend
44mJavaScript in 2017: You might (not) need a framework
42mIntegrating React Into Legacy Projects
28mLessons in Managing Technical Debt
27mUnderstanding JavaScript Libraries via React and the React Ecosystem
45mDeconstructing React and The Web Platform Delta
34mI Heard React Was Good
44mWhy I Stepped Away from React in My TypeScript Projects and Where I Went