4 ms·
I think my favorite part is that this is so outrageously unheard of that the error isn't even CSS-styled correctly. Zero left margin, just up against the edge o
by aerovistae 4y ago
I think my favorite part is that this is so outrageously unheard of that the error isn't even CSS-styled correctly. Zero left margin, just up against the edge of the window. Nobody even thinks about this case of an error being displayed because it's so rare.
- soheil 4y agoCan't be that unheard of. Here it is in 2020 https://support.google.com/websearch/thread/29809009/google-search-internal-server-error https://support.google.com/websearch/thread/29809009/google-...
- comboy 4y agoGiven amount of searches, your counterexample being from 2020 seems to be just proving the point. But I would imagine in most cases, when there's backend error you could fall back on some simpler engine and display that without user having any clue.
- exikyut 4y agoIt also makes me think that there's probably broken ownership of the plumbing around the obviously-novel routing/layout/presentation path taken when this error is shown. A while back while poking around I landed on an interstitial page of some kind using an old 2005-era Google logo, which was cute. Obviously nobody'd noticed and submitted the page in question to whatever bit of internal gunk was presumably used to track where the logo needed updating. But that makes me wonder - the glitch I saw was a platform-level thing easily missed - but is Search that much of a vast, not-particularly-cohesively-integrated expanse too?