People wondering what Chrome has to do with a search monopoly:
The obvious benefit is that they can default the user’s search provider to Google.
But the more nefarious benefit is that, by controlling both the client and server, they can unilaterally decide the future of web standards. They don’t have to advocate for proposals, gain consensus, and limit themselves to well-supported standards the way other companies do. They can just do it, gain the first-mover advantage, and force others to follow suit.
If they don’t like HTTP/2, they can invent their own protocol and implement it for their search servers and Chrome. Suddenly, using Chrome with Google Search is way faster than using Chrome with Bing or using Firefox with Google Search. Even if Microsoft and Mozilla don’t like the protocol, they now have to adopt it or fall behind.
This has happened. QUIC was deployed in 2012. Firefox gained support in 2021.
They’re doing the same thing with Privacy Sandbox, and you can also look at browser feature compatibility tables to see how eager Google is to force their own interpretation of every not-yet-finalized web standard as the canonical interpretation.
My most successful standups have been like:
“Okay, we’re all here. Anyone wanna take a look at anything together?”
“I need some help with XYZ. Alice, can you take a look?”
“Sure.”
“Anything else? No? Alright, let’s do it.”
Typically less than 2 minutes of whole-team time, at our desks. Really just a reserved pivot point where it’s okay to interrupt each other’s tasks to ask for some pairing time. Sometimes an unofficial second one would happen after lunch.