And yes, I'm planning to write a ~~bug~~ ~~blug~~ blog post about that :)
"Apple's WebKit performance tax leaves iOS browsers stuck in the slow lane, says Microsoft"
www.theregister.com/software/202...
The State of CSS 2026 survey. Take a minute to fill it in. It really, *really* helps!
survey.devographics.com/survey/state...
The world’s first trillionaire is a killer
www.theverge.com/tech/949259/...
Oh and in case you're wondering how l/v/h viewport units are broken on iOS (especially 26+):
bugs.webkit.org/show_bug.cgi...
bugs.webkit.org/show_bug.cgi...
bugs.webkit.org/show_bug.cgi...
Why is this so exciting?
Because right now, every single browser on iOS runs on a very specific build of the WebKit engine that ships with the OS, a build that Apple controls.
Why don't they ship their own engine?
Because Apple's App Store rules say so.
open-web-advocacy.org/blog/apples-...
Newly published tests show a Chromium/Blink engine running on iOS is 28.6% faster than Safari in Speedometer page responsiveness tests. 🏎️💨📱⚡️
This is a clear example of the costs Apple imposes on consumers and businesses, costs created by its 17-year ban on competing browser engines.
🧵👇️ (1/8)
Safari 28.6% slower than Chromium on iOS. This is the tax every single user on iOS has to pay as a result of the #AppleBrowserBan
www.theregister.com/software/202...
Chromium *with its own Blink engine*, running on iOS. 👀
Faster than Safari. Supports features that Safari doesn't. Presumably ships with l/v/h viewport units that are not utterly broken.
And this is just a prototype.
www.linkedin.com/pulse/test-d...
1/n
This has been a common theme today at #cssday and it’s true: complaining about broken stuff in browsers is a great way to get them fixed!
Don’t silent. Let us know.
Have a new idea: write a blog post!
