4 ms·

I doubt the core Chrome team agrees with that. This was said by someone in charge of negotiating search engine deals for Android and such, not someone in charge

I doubt the core Chrome team agrees with that. This was said by someone in charge of negotiating search engine deals for Android and such, not someone in charge of Chrome. I'm sure the Chrome people see the ads people as a wallet for their development as much as the ad people see the Chrome people as a vessel for their ads. In the end the ads people bring in the money so they'll probably get their way, but last time this case came up on the front page there was an example of the quick search feature testing well with users (clearly originating from thr Chrome team) clashing with ad delivery, and only after the ad people raised an issue did Google turn back the changes. This suggests to me that the ad people have some influence on the decisions the Chrome team makes, but the two teams clearly have very different goals in mind.

djbusby 3y ago
Different goals maybe. The outcome from that case was that Ads won. Does the goal of the Chrome team matter when they are blocked from implementation?
lolinder 3y ago
> This suggests to me that the ad people have some influence on the decisions the Chrome team makes, but the two teams clearly have very different goals in mind. Yes, they have different goals, but you're downplaying the amount of influence from ads that this incident suggests—when the org was forced to choose between keeping a feature that was shown to serve users or scrapping it to make the ads team happy, they scrapped it. In the end it matters very little what the Chrome team would prefer if the corporation consistently overrules them.