8 ms·
(I used to work on the webserver for Google Search. Left Google several years ago, have no more vested interest in them.) The reason for the browser-sniffing
by nostrademons 9y ago
(I used to work on the webserver for Google Search. Left Google several years ago, have no more vested interest in them.)
The reason for the browser-sniffing in search is a combination of ease of testing + latency reduction. By supporting a known set of browsers, you can write a test plan for each and shard it out among contractors (or ideally, automate it with a Selenium config). Manual tests run on every release (2/week when I left, maybe more now), and automated tests run on every changelist (thousands/week), so you can see how adding additional browsers to the testing matrix can consume significant resources. Very often cutting-edge features will launch on Chrome only and then if users like them, they'll get ported over to all the other browsers. (Or, just as often, the project is canceled and the feature is unlaunched on Chrome a year later, which IMHO isn't a great habit on Google's part but it is what it is.)
If you're manually spoofing your user agent, then Google figures that you know what you're doing and it's "use at your own risk anyway", and that if you get a broken experience, your first thought will be to disable the user-agent spoofing.
Additionally, browser-sniffing lets you serve only the JS needed for that particular browser, and not all of the hacks/polyfills/bugfixes/workarounds needed for browsers that the user isn't using. This is probably less of an issue now that things are more standard, but when I started ('09), not needing to serve all of the IE6 workarounds when the user was on Chrome or Firefox saved a lot of latency for users that were on modern browsers.
- forapurpose 9y ago> you can see how adding additional browsers to the testing matrix can consume significant resources Google has the resources to test all the browsers it wants to. Perhaps part of the reason that companies with their market power tend to act this way is that serving other browsers becomes a low priority, and why should we help the competition anyway?
- fuck_google 9y agoWhy the downvotes? Because its obvious?
- kuschku 9y ago> If you're manually spoofing your user agent, then Google figures that you know what you're doing and it's "use at your own risk anyway", and that if you get a broken experience, your first thought will be to disable the user-agent spoofing. Actually, some browsers, including Firefox Mobile, now spoof the user-agent by default on some sites, because of Google's broken systems.
- Endy 9y agoThis strikes me as both a bad sign about Google's direction and Mozilla's willingness to accept that without publicly calling them out as Vivaldi just did.
- fbender 9y agoMozilla did multiple times and is doing it, sometimes even doing the work that Google is supposed to do (see e.g. the Webcompat project [1]). The point is, this problem is basically unsolvable without having the reach of Google and thus everone (incl. Microsoft!) is forced to spoof the UA. See also https://webcompat.com/ https://webcompat.com/
- Endy 9y agoNo company is "supposed" to do anything in my eyes; and I'd rather if they all did a lot less that wasn't defined as "produce this one very specific product that does one thing well". If anything, the agencies that are supposed to do anything for the infrastructure of the Internet are the various governments and the UN, to support an open Web. The problem is that at present the US, UK, Russia, China, North Korea, and several other key nations are trying to destroy the open Web, so it falls to companies, who are better off setting up their own walled gardens and forcing every user into the digital equivalent of the old mining company towns. We need to stop bending to any of these groups just because they're "the big guy". If the largest Web company is building "free" and "open" stuff in an anti-competitive manner, then make sure that's painfully obvious to the end-user, make it public (i.e. an NYT article's a nice start) and then file federal lawsuits, calling on users as witnesses. The people of America beat the Robber Barons before, I don't understand the reason why we are so unwilling to do so now that they've moved to the Web. Stop spoofing, stop capitulating, stop compromising, and start fighting back.
- nialv7 9y agoI interned at Google once. And the first thing they told us at the orientation is that they put the users first. Is that a lie then? Because what you said seems to imply Google puts the convenience of the developers first.
- mining 9y agoDepends how you look at it. Dev time is a finite resource, and spending it on supporting a weird combo of user agent and browser seems likely to lead to less user utility.
- ricardobeat 9y agoWeird combo being Firefox with its default user agent..
- squeaky-clean 9y agoWell, mobile Firefox which is much less common.
- kuschku 9y agoOr Desktop Firefox (~43% of German desktop market) in Google Inbox (during the launch), the new YouTube redesign, Hangouts, Allo, Earth... Half of Google products either don’t work at all, or far worse, on one of the largest browsers out there.
- deleted 9y ago[deleted]
- rasz 9y agoAdword/Doubleclick clients are their users, not you and me.
- WalterSear 9y agoI'm not so sure. I've witnessed their adwords team plunder a startup marketing team's budget with false promises and bad advice.
- vram22 9y agoI was just going to ask why search should be browser-specific, until I read your last paragraph.
- fbender 9y agoTry progressive enhancement, or at least graceful degradation. Displaying a freakin' search field shouldn't be that hard. And finally, why not load the necessary polyfills and fixes on demand? When the old/slow browsers need time to get ready, a few hundred milliseconds more or less don't matter.
- int_19h 9y agoThe real problem here is optics. There are certainly many valid technical and business reasons to target specific browsers - we've heard them all back in the day when "Best viewed in Internet Explorer" was a standard disclaimer on more than half of all websites out there. That arrangement did not work to the advantage of either the users or Google, though. So Google invested significant resources in web standards and alternative browsers, breaking the Microsoft monopoly. But now that Chrome is rapidly approaching the position that IE held, the users and the web developers are getting a feeling of deja vu, and Google's behavior - however motivated - plays right into that.