The more I tune into JS framework discussions the more Iβm concerned at how few developers seem to be concerned with how their work is actually delivered. Browsers are optimized to receive websites as HTML first, yet frameworks taught a generation of developers to build blogs like they are executable files to load & boot. I was asked twice this week if I think server components are a good idea (?). Yes! Create react app was a poor fit for most sites. Stop building the Web like itβs an App Store.
Scott Jehl
Scott Jehl
npub133e0...rqrd
Independent Web Designer/Dev. Accessibility & Performance Fan. Author, Speaker, Mediocre surfer. Working on a Web Components course!
Alum: WebPageTest, Filament Group, jQuery
Website: https://scottjehl.com/
Web Components Demystified: https://scottjehl.com/learn/webcomponentsdemystified/
Blog: https://scottjehl.com/posts/
Web Performance Course: https://www.webpagetest.org/learn/lightning-fast-web-performance/
I've audited a lot of large-scale server-rendered single-page-app sites in the past several weeks and it's clear that 1: frameworks finally serving HTML up-front is a welcome (long overdue) change, and yet 2: chasing it with a typical 1-to-6+ megabytes of "rehydrating" JavaScript means a lot of people are getting a site that may look usable but feels very broken. You can find them in the p25 that aren't getting "good" core web vitals.