Published on 04.12.2025
TLDR: Alex Russell's annual analysis reveals that while the web gets faster for those with high-end devices, the performance inequality gap is widening. He argues that developers' focus on expensive JavaScript frameworks and their ignorance of real-world device and network constraints are creating a web that increasingly punishes the less affluent and undermines business goals.
Link: The Performance Inequality Gap, 2026 - Infrequently Noted
TLDR: After nearly 14 years, Addy Osmani, a prominent figure in the web development community and a key engineering manager on the Google Chrome team, is moving to a new role within Google. In a heartfelt farewell post, he reflects on the incredible evolution of the web platform and the collaborative efforts that shaped it.
Link: Farewell for now, Chrome.
TLDR: In a fiery op-ed, Alexander T. Williams argues that CSS-in-JS, once seen as a solution to styling woes, has become a performance-draining, over-engineered "ticking time bomb." He makes a compelling case for returning to native CSS solutions, which are now more powerful and capable than ever.
Link: CSS-in-JS: The Great Betrayal of Frontend Sanity
TLDR: A wave of new and upcoming browser features like CSS Masonry, the Popover API, and View Transitions are set to replace common JavaScript libraries. This shift promises better performance, improved accessibility, and simpler codebases by leveraging the power of the native web platform.
Link: Masonry: Things You Won’t Need A Library For Anymore — Smashing Magazine
scrollbar-gutter: stable;, you can reserve space for the scrollbar, preventing the page content from jumping when the scrollbar appears or disappears. This is now supported in all major browsers.<dialog> is open with just CSS. A recent change to overscroll-behavior in Chrome 144 allows you to apply overscroll-behavior: contain to a dialog (with overflow: hidden) to stop the underlying page from scrolling, solving a long-standing annoyance.Links: