Thanks to 20+ years of cooperation via standards, most web devs are insulated from the reality that competition (or the threat of it) makes standards possible. It's a shock to recognise that Apple has broken the system so thoroughly that SDOs themselves are at risk:
One assumption made web standards possible: competitors are free to ship differing ideas when they disagree. Until iOS, this was the norm. Apple's ban on competing browser engines changed that, and Cupertino is poisoning the roots of the tree that gave the web life:
Cory Doctorow (@npub1fdrp...lvhs) quipped: *"An 'app' is just a web-page skinned in enough IP to make it a crime to add an ad-blocker to it."*,[1] but the native rot goes deeper. Remember when FB rebuffed Apple's offer it couldn't refuse?[2] Knock me over with a feather, the "privacy wars" were all for show: [1]: [2]: https://www.phonearena.com/news/apple-facebook-almost-worked-together_id141910
I want you, a tech-literate person, to internalize one deep fact: Apple vs. Facebook is, and always was, kayfabe. In reality, Apple is (and always was) Facebook's chauffeur; holding its coat while it surveilled everyone. How to be sure? IABs: Apple facilitates mass surveillance through native apps from Facebook, both directly from in-app activity, but much more insidiously, through "in-app browsers" that FB tacks onto every link you tap. And these things are *rank*.
Several times over the course of my career, specific companies have gummed up the works in web standards, leaving it to everyone else to figure that out they weren't on board with the web continuing to progress. It's bad, and we should learn to spot it:
An extremely cool ping/pong of ideas teasing out what good browsers can do with almost no code in these posts:
I spent hours and hours trawling through the sites of some of the world's best web developers, and despite the horrors I regularly experience in my daily work in Big JavaScript Territory, what I saw left me hopeful:
Just published a new section on my site to capture references to a lot of the essential web performance and fundamentals-oriented webdev resources I find myself continually directing folks to. Also, lots and lots of links to blogs I love:
The dirty JS hacker in me loves this (ab)use of `PerformanceObserver` so much:
I've been pretty lax about keeping up with the webperf slack, but this was in the scrollback from March, and I love that it shows so directly how understanding the rendering engine unlocks better experiences for everyone, not just folks on low-spec machines and networks: