Rick Byers

Rick Byers

@rbyers.net

Web Platform engineer at Google on the Chrome team, helping the open web to thrive. Opinions are my own, not my employer's.

640 followers183 following210 posts

Nom-EU immigration in Brussels is awful! My 3 hour wait is apparently now typical in the morning rush. I could have saved an hour (and at least 2 productive hours) by flying to Amsterdam instead and taking the train!

Rick Byers reposted

This is the best explanation of the interplay of specs, tests, and implementations that I've read. The point of both specs and tests is interoperable implementations, but that doesn't mean that implementations are always right when they agree.

Happy 25th birthday @igalia.com. I am so inspired by the lasting value you have contributed to the web and society at large, and even moreso by your unwavering values in implementing that work. Here's to the next 25 years indeed! www.igalia.com/2026/09/21/T...

igalia.comTwenty-Five Years Upstream | IgaliaIgalia is an open source consulting firm specialised in the development of innovative projects and solutions. Our engineers have expertise in a wide range of technological areas, including browsers an...

I just finished reading the excellent book "Incorruptible: Why Good Companies Go Bad and How Great Companies Stay Great". Igalia seems to fit the pattern of great long-term companies (Costco, Vanguard, Patagonia, Devoted Health, etc.).

Software is becoming intensely personal and disposable. An app built with AI just for me and my use case is becoming "better" than the best generic software. The web is designed to handle this explosive scaling and so is poised to be the dominant platform for the future of personalized software!

I finally know what caused me to have to cancel my BlinkOn 4 trip four years ago!

Rick Byers Lab@lab.rbyers.ca

Four years ago I missed my favourite conference ("BlinkOn") for a bad cold. It's been the biggest frustration of my lab that I couldn't find the virus that caused it. Now, that I have a 32-way panel from YouSeq.com I finally know why: It was a bacteria, H.Influenzea, not a virus at all!

Rick Byers reposted

🎙️ Check out Bruce Lawson’s interview with Alex Moore, executive director and co-founder of Open Web Advocacy. They explore OWA’s history, why it exists, and what it’s fighting for: a better, more competitive web 🌐✊ open-web-advocacy.org/blog/bruce-l...

open-web-advocacy.orgBruce Lawson Interviews OWA: For A Better Web - Open Web AdvocacyCheck out Bruce Lawson’s interview with Alex Moore, executive director and co-founder of Open Web Advocacy. They run through the history of OWA, why OWA exists…

Hey Claude, feel free to just tell me you're pissed off that I'm micromanaging you and getting in your way, I won't fire you I promise. 😂

Oh oh, I seem to have become addicted to Claude tokens! Probably late to the party, but I keep upping my spend limit. I'm at $400 so far this week 😬. This is because I thought I could build my own version of something that cost $2800 to buy, we'll see if I end up saving money or not 😊.

I am a negligent husband! I just discovered my wife's MacBook was running MacOS 10 and so stuck on Chrome 128 and missing 2 years of security patches! If even I fail to keep my family safe online we might be doing something wrong 😕.

Given how Chromium and WebKit are always vying for the top spot in Speedometer on MacOS, it's really striking how big the gap is on iOS! And we haven't even really tried to optimize performance for that platform yet! IMHO this is what you should expect to see when there's a lack of competition!

A great analysis! The punch lines: "The trend is clear: for every 100 milliseconds slower a store loads, conversion tends to be about 3.5% lower." "For every 32 milliseconds slower a store responds to interactions, conversion tends to drop by about 1.5%."

Mateusz Krzeszowiak@krzksz.bsky.social

One of the most important pieces about web performance that I've ever worked on is finally live. After a few months of work, my analysis of the correlation between site speed and conversion across the entire @Shopify platform is out: www.shopify.com/enterprise/b...

Rick Byers reposted

Replying to @gordon.bsky.social

I think part of the phenomena here is that it is easy to predict things will fail: most things fail. So, stop energy is much cheaper to produce, because you would be right 99% of the time. Against-everything-for-nothing is a comfortable stance to take, but long term it is the 1% that move forward.

Next step: vibe code a replacement for concur so I can file my BlinkOn trip expenses in 1/10th the time? 😜

Someone in my family asked what they can say to a tech support scammer calling them to confirm they are a scam, not a legitimate company. Thoughts?

View full thread

I figured a scam will be left either trying to convince the victim to use a different communication mechanism, will be forced to give the address of a legit company whose contact form won't reach them, or will risk Google Safe Browsing block and takedown action.

In this case it's a repeat call from one company in particular which previously scammed my family member out of $200, hoping to repeat their success. I'm frustrated that VISA has so far refused to issue a chargeback, even though I have photos like this documenting the obvious scam.

Someone in my family asked what they can say to a tech support scammer calling them to confirm they are a scam, not a legitimate company. Thoughts?

My best suggestion: "I'm busy right now but if you give me your website address, I will reach out through your contact information there". Don't accept a phone number or other form of contact. Any legitimate IT company will have a website with contact info that works.

Rick Byers reposted

I'm excited about FedCM ambient UI. Balancing tough tradeoffs is one of the hardest things we do in Chrome and the only way to do it well is to experiment heavily and collect user feedback.

Sam Goto@sgo.to

I'm putting together a chrome://flag in canaries that enables the FedCM's Ambient UX in the URL bar. I've been using it for a week or so: it is beautiful and I think it will have arrive at an economic equilibrium. Here is the before / after, how to enable it and why we are working on it:

Rick Byers reposted

Chrome is announcing that they are moving into a two-week release cycle! Exciting bc the web needs to move quickly- resolving bug fixes, feature improvements, etc. It goes along with devops principles of shipping smaller, more frequent releases for stability developer.chrome.com/blog/chrome-...

developer.chrome.comGet features faster with Chrome's two-week release cycle  |  Blog  |  Chrome for DevelopersFrom September 2026 Chrome releases will be every two weeks.

That feeling when a family member shares photos like this 🤬😭. I spent much of Sunday formatting and reinstalling Windows, and formulating a credit card transaction dispute.

I hosted a number of visiting global Chrome leads in Waterloo this week. Several had never seen snow quite like we had today, so of course we had to take them tobogganing. Looks like we'll be doing Chrome leads summits in Canada every winter now 😂.

Progressive enhancement is really important for enabling the best possible user experiences for everyone!

Josh W. Comeau@joshwcomeau.com

This looks OK, but it would be so much more satisfying with more particles. Check out how nice it is with 70 particles instead:

Rick Byers reposted

✨ Exciting proposal alert: the CPU Performance API. This proposal will add `navigator.cpuPerformance`, a value that measures the broad performance capability of the CPU. That way, we can scale up/down our animations to make sure everyone has the best experience possible for their device. 😄

github.comGitHub - explainers-by-googlers/cpu-performance: An API that exposes some information about how powerful the user device is.An API that exposes some information about how powerful the user device is. - explainers-by-googlers/cpu-performance

I just almost made a dumb mistake. I've been enjoying Kurzgesagt videos for years (on various devices). After watching their video on AI slop I figured it was time to support them on a recurring basis, so I hit the join button... youtu.be/_zfN9wnPvU0?...

youtube.comKurzgesagt – In a NutshellAnimation videos explaining things with optimistic nihilism since 12,013. We’re a team of illustrators, animators, number crunchers and one dog who aim to spark curiosity about science and the world ...

I almost completed it until I noticed the text "cancel at any time in Apple settings". Wait, oh right, only 49% of my money will go to the creator! 21% to YouTube for the platform/serving and 30% to Apple for ... what exactly?

So I subscribe on Android instead and see it's about 25% cheaper there ($2.99/mo vs. $3.99), with the creator presumably getting the extra 5%. Yay!

It was fun to be part of this, thanks Henri! I wasn't able to join the livestream for the rest today but really looking forward to listening to it over the next couple days!

Henri Helvetica 🧑🏾‍🚀🇭🇹@henrihelvetica.bsky.social

✨ Core Web Vitals Summit ✨ stream is today in just over 1hr, @ 11am, virtual doors will likely open a few minutes before. Join us! Hang out. Come hear from web performance and ux professionals. 📆 TODAY, Wed Dec 3rd ⏰ 11a EST, 5p CET 🔗 bit.ly/cwv-summit

Lots of people incorrectly claiming Chrome/Google "tried to kill JPEG XL". Just because an engine chooses not to be the FIRST to ship a new technology does NOT mean they are trying to kill it!

View full thread

I think it's fair to criticize the Chromium project for apparently getting the initial cost/benefit prediction wrong on JPEG XL. But the fact that JPEG XL is moving forward anyway is a success to be celebrated in the consensus-forming process of the web platform! groups.google.com/a/chromium.o...

Now, if two engines have shipped a feature for an extended period and the third is still holding out, that's something to be suspicious of! We are always keeping an eye on the data to try to ensure Chromium isn't holding back interoperability. webstatus.dev/stats

Lots of people incorrectly claiming Chrome/Google "tried to kill JPEG XL". Just because an engine chooses not to be the FIRST to ship a new technology does NOT mean they are trying to kill it!

It's good and healthy for different browser engines to have different opinions on the cost/benefit tradeoffs of features. This is what we want from "engine diversity" after all, right? But then we each watch the public signals of the others when deciding what to ship.

When we first reviewed JPEG XL, as far as we could see no other browser engine wanted it. Our judgement was the benefit wasn't worth the cost. Then Safari decided otherwise and shipped it. Once Mozilla expressed their openness to shipping, it was inevitable that Chromium would too.