Google's Precision Is Getting Worse

… or maybe this is not a recent change at all, I don’t really know. Long ago I blogged before about the ways Google misunderstands me, and nothing has changed on that particular count. Today I noticed that there’s a new way Google intentionally misinterprets my query. Weird. So, I was searching for Comparer (try it yourself). Right at the top of the page, Google says this:

Showing results for Icomparer. Search instead for Comparer

Brilliant, eh? I’m starting to think it would be good if Google could have a programmer’s mode or something. Actually, just call it a accept my queries as they are please, I now what I’m doing mode. I can’t even guess why it’s doing this thing with Comparer<T> – once I click that link in the prompt, there are several results with that precise string in the page title. The URL changes to this, btw:;q=Comparer%3CT%3E&amp;nfpr=1

That nfpr parameter seems to make all the difference. So maybe bing doesn’t have that problem? No, it doesn’t. But then it doesn’t try to suggest anything on that search string either, so I guess somebody could call this a missing feature instead. Oh, and bing doesn’t solve that old problem with “special” characters either – they seem to have established a special case for the term “.NET” (surprise surprise), but searching for something like “.text” or even for help on regexes with “.+?” fails just as miserably as ever.

Sorry, this blog does not support comments.

I used various blog hosting services since this blog was established in 2005, but unfortunately they turned out to be unreliable in the long term and comment threads were lost in unavoidable transitions. At this time I don't want to enable third-party services for comments since it has become obvious in recent years that these providers invariably monetize information about their visitors and users.

Please use the links in the page footer to get in touch with me. I'm available for conversations on Keybase, Matrix, Mastodon or Twitter, as well as via email.