Always crashing in the same car (the state of front end web development in 2022)
summary
Two months of reading and 100 tabs lead to the claim that performance and developer experience drive today’s chaos: SPAs bloat with JavaScript, SEO hits push server-side rendering and partial hydration, and new tools (Next.js, Remix, SvelteKit, Astro, Solid.js, web components, and Mitosis) each promise fixes. Real examples: a 10‑year app proves longevity and low complexity, a hastily adopted React rewrite introduces upgrade and CSS bloat (25 stylesheets) that slow everything, so spike real workflows and choose stack by goals not hype.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 2:26How did we get here
- 3:09The browser war
- 11:30Silverlight
- 12:59Current state of play
- 14:42Performance
- 16:14Single page applications
- 19:04Serverside rendering
- 19:46Zero JavaScript
- 20:34The learning curve
- 22:58React vs Angular
- 23:52SolidJS
- 25:39Web Components
- 26:54Myxomatosis
- 28:17Angular
- 32:48What do developers do
- 34:41My personal opinion
- 36:10Small thoughts
- 37:36Dont believe the hype
- 39:25Look at your overall scope
- 44:08Know your HTML
- 46:02Component CSS
- 49:45Review your assumptions
- 52:05Use the platform
- 54:33Summary
- 56:34Questions
related talks
21mDante’s Inferno of Fullstack Development (A Brief History)
29mQuo vadis, frontend?
43mRethinking SPAs: web-native apps
29mPreprocessors, Components, and CSS in JS or: How I Learned to Stop Worrying and Love the Website
21mFrontend-centered Development: the Future of Web Development
44mServer Side Rendering from the trenches
32mWhat's Happening in the JavaScript Ecosystem?
45mGive Me Back My Frontend!