惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
博客园_首页
雷峰网
雷峰网
V
V2EX
博客园 - 司徒正美
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - Franky
月光博客
月光博客
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学
T
Tailwind CSS Blog
小众软件
小众软件
博客园 - 叶小钗
美团技术团队
酷 壳 – CoolShell
酷 壳 – CoolShell
Apple Machine Learning Research
Apple Machine Learning Research
IT之家
IT之家
MyScale Blog
MyScale Blog
Blog — PlanetScale
Blog — PlanetScale
大猫的无限游戏
大猫的无限游戏
Jina AI
Jina AI
人人都是产品经理
人人都是产品经理
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻

Chris Coyier

The Avocadinator Which Rude is it? The Four Tiers of Tab Importance Underdesk Treadmill I’m done with this podcast! (UX request) 46 Clips from Hacker News Thread Outburst chriscoyier.net CodePen 2.0 Choosing Movies How You Get the Mentos into the Diet Coke chriscoyier.net The Raven Tattoo Sprinter Van Phone Mount + Better CarPlay-Compatible Cable Situation The New Van Social RSS (?) Did your editor font go default serif on WordPress 7.0? When Sites Need to Walk Away AI & Alignment Bette Midler sings Woodie Guthrie Stories from Alaska Folk Fest 2026
It’s an assumed truth that Safari is better for battery l...
Chris Coyier · 2026-04-24 · via Chris Coyier

This pseudo-truth just bugs me.

I hear it all the the time. People saying they choose Safari as a browser because it’s better for their battery. But there isn’t any data (that I know of) that proves that Safari is more efficient at battery usage than any other browser.

I applaud Matt Birchler who did real testing on this (2024). He scripted a 20 minute loop that watched YouTube videos, scrolled Mastodon, scrolled websites, and typed in Google Docs. He ran it in Chrome vs Safari for 3 hours each 6 times. The data actually showed Chrome was a little bit better.

You can choose Safari because you like how it feels, or it’s support of certain features, or heck even because it’s the default browser on Apple stuff and sometimes it feels good to just go with the grain. But the battery life argument just doesn’t hold water.

Maybe it did at one time!

Remember when we used to care about CSS selector performance, then people like Steve Souders, Nicole Sullivan, Ben Frain, Harry Roberts, etc did testing and proved it mostly just doesn’t matter?

Remember when inline CSS was always bad, then it turned out to become a recommended performance enhancement sometimes?

Remember when we all put scripts at the bottom of the <body>, then we got the defer attribute and it turns out its often better to leave them in the head now?

Remember when FOUT as bad (layout shift!) then it was good again (users don’t like seeing nothing!)?

Sometimes we gotta just update our thinking. I’m sure I’ve got loads of outdates factoids in my head that need a reboot.