Quo vadis, frontend?
summary
Claims concrete tradeoffs: http/3 over QUIC reduces connection stalls, browsers except Safari gain measurable speed; bundlers and Vite + webpack 5 module federation shrink shipped bytes; rendering engines and proposals like worker DOM push frame rates toward 60/120 FPS while SSR frameworks such as Remix and Next.js reduce client JS; component-level data fetching via React Query and SWR and backend services like Supabase and AWS Lambda let one-developer products ship fast but raise costs and vendor lock-in; web vitals, accessibility laws, and Fugu platform APIs are already actionable constraints.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:30About Evgeny Kot
- 1:25Biggest problem in frontend
- 2:06History of frontend
- 3:01Top 10 frontend trends
- 6:49Fastest rendering engine
- 9:43Multiple stores
- 17:57Web platform
- 20:08Package delivery
- 20:37Micro front ends
- 21:05Multiple teams
- 22:05Reusing code
- 22:46One man team
- 23:05Web developer
- 26:20Typescript
- 26:39Future trend
- 27:52Web 30 hype
- 28:49Conclusion
related talks
32mWhat's Happening in the JavaScript Ecosystem?
40mThe state of frontend frameworks in 2023
25mFrontend is dead, long live full stack
30mMicro Frontends in React — a State of the Art Approach
53mThe Future of Frontend
31mThe Future of Front-End Performance
28mFantastic Frontend Performance Tricks & Why We Do Them
29mNew Trends in Front-End Development (and What We Can Learn from them)