if you add enough JavaScript, it will modulus your site back to fast again—we just haven’t found the threshold yet—stay the course everyone, keep adding more!
17 replies
@zachleat lighthouse scores are unsigned ints. Once they try to go below 0 it’s back to blazing fast!
@zachleat The DOM is the problem, Zachary, my man! If we just render the whole page with Canvas we can avoid that. We’ll have to ship before we figure out the a11y problem, but we can always figure that out latter. Blind people only make up like 1% of the population, anyway.
@thefinley this satire is grounded in entirely too many real things that have been said by folks
@zachleat You and me both, my friend. You and me both.
@zachleat same energy https://youtu.be/lmmp7fGAgRg
@DavidDarnes we should cancel mr bean
@zachleat I want to frame this post.
@zachleat I'm actually experiencing this with hydration re-rendering LCP, with enough throttling LCP timing is good again 🙃🫠
@clarkgunn ha! pre-JS LCP must be fine as long as hydration takes long enough? 😅
@zachleat yup, so happy with the "throw everything away and re-render" programming model.
@clarkgunn *runs away*
@zachleat this feels like it needs a Kylo Ren Moar meme or a Leo Inception Go Deeper meme. Make this an Epic Modern Web Shit Post Zach … you can do it ! 😝
@thomasapowell NOTHING IN MODERATION
@zachleat We should store the JavaScript in the favicon. This way when the website icon is displayed in Google’s results list, it magically preloads the JavaScript!
@meduz this is a super villain origin story