Back in September, Codinghorror wrote a popular post on the state of android Javascript performance on Discourse’s Meta forum. It drew a lot of attention, and led to some fascinating discussions …
Exciting Improvements Delivered Today in Firefox for Desktop and Android | The Mozilla Blog
Today we’re proud to announce the initial rollout of multi-process Firefox for Desktop to our general audience. With this, we’re taking a major step fo
The many, many, many JavaScript runtimes of the last decade
This last decade has seen an inundation of new JavaScript runtimes (and engines in equal measure), enabling us to run JavaScript in all manner of contexts...
Experiments with Google
Since 2009, coders have created thousands of amazing experiments using Chrome, Android, AI, WebVR, AR and more. We're showcasing projects here, along with helpful tools and resources, to inspire others to create new experiments.
Web Engines Hackfest 2025
Why I switched to Android after 7 years of iOS
Monday of last week I was all excited. I had just gotten the green light to start prototyping a new Progressive Web App for a client I've been working with.
Our best practices are killing mobile web performance
Web performance rules invented for desktop web access need to be revised for the mobile era.
State of the Art JavaScript in 2016
State of the Art JavaScript in 2016 So, you’re starting a brand new JavaScript front end project or overhauling an old one, and maybe you haven’t kept up with the breakneck pace of the ecosystem …
Next.js — The Perpetual Beta Framework
Exploring 6 years of Next.js, from early days to App Router & RSC, with migrations, performance tweaks, and framework insights
Turbocharging Web Apps: Efficient AI Model Caching in Chrome
🎬 Watch The Android Show | I/O Edition 2026
Solving Performance for 2D & 3D Web Apps: Finally!
Reckoning: Frontend's Lost Decade | Alex Russell | performance.now() 2024
I Built the Same App 10 Times: Evaluating Frameworks for Mobile Performance | Loren Stewart
I needed to choose a framework for a mobile-first app at work. I started comparing Next.js, SolidStart, and SvelteKit, then expanded to 10 frameworks. The measurements revealed dramatic differences in bundle sizes, performance, and the real cost of framework choices.
Maybe we could tone down the JavaScript
I’m having a really weird browser issue, where scripts on some pages just won’t run until about 20 seconds have passed. Whatever you’re about to suggest, yes, I’ve thought of it, and no, it’s not the problem. I mention this not in the hope that someone will help me debug it, but because it’s made me acutely aware of a few… quirks… of frontend Web development. (No, really, do not try to diagnose this problem from one sentence, I have heard an
