That you probably don't want the thing you're searching for, but some alternate spelling, even if it's something completely different.
I imagine this probably ends up being the case for the majority of their users, but for advanced users and people searching for specific technical strings, they've cheapened their service.
> we didn't make any change *in terms of retrieval*
Users don't care which part of the system was changed to cause the results to be worse.
It looks like maybe your reply is only about what changes recently shipped and are mentioned in the blog post. A lot of the discussion in this comment section is about changes much older than these changes.
It may be true that quotes are working the way we expect, but the data set to which they apply is very obviously restricted before they get a crack at it.
Probably the vast majority of the population have no idea that quotes do anything in searches. Maybe they need some checkbox in the tools bar that makes quotes actually work if you know how they work.
they do this for other things that annoy the F out of me. for example, searching for a phone number. it's a specific set of numbers that is unique. if there's no results for that number (or very few), it gives me results for numbers that are similar like same area code, same prefix, different number. nope. that's not useful. in this situation, I'd much rather see that no results are found rather than making me think there's a result but forcing me to look closely that it is what I wanted