The Victorian Age of JavaScript
summary
Modern front-end work generates surprising overhead: an Angular QuickStart can produce 108 megabytes and 13,740 files, 39 requests and 2.2 MB transferred just to show an H1. Single-page apps are often unnecessary for line-of-business sites; prefer static site generators, server-rendered templates or PJAX-style HTML fragments. Use NPM not Bower, choose Webpack or simple NPM scripts for builds, be cautious with Babel stage presets, favor TypeScript or plain ES5 where suitable, and consider React and Redux plus async/await for manageable complexity.
AI-written summary · about
chapters (14)
- 0:00The Victorian JavaScript era
- 2:58JavaScript advancements
- 4:46Dangerous trends
- 6:20The case against Angular 2
- 9:38History of web development
- 12:37Renaissance to fatigue
- 14:17Rendering strategies
- 16:41Package management
- 21:57Transpilers and tools
- 26:51Build systems
- 30:54Async management
- 36:19Framework evaluation
- 41:30The case for React
- 45:17Conclusion
related talks
47m2017 DevFestMN Eric Brandes
41mYou Really Don't Need All That JavaScript I Promise
45mDid We(b Development) Lose the Right Direction?
58mAlways crashing in the same car (the state of front end web development in 2022)
59mASP.NET Core for Angular, React, Knockout etc developers
53mThe Unbearable Weight of Massive JavaScript
40mThe state of frontend frameworks in 2023
22mPerformance Empathy