This is great. I feel Google has slowly become too user friendly. My mobile results are always way less technical than my desktop results. If I'm in the car (passenger) and want to look up a problem I'm having while programming, I get mostly related queries that are a simplified version of what I'm looking for.
I really believe that the technical crowd drives what becomes popular (app recommendations for family and friends). I feel a lot of the "Google hacking" queries have become less obvious and the search bubble stuff was getting bothersome. This is definitely a step in the right direction. Hopefully I'll be a little less frustrated with results in the future.
Google tailors its results to the kind of person it thinks you are. For example, if you immediately search "python", you will get results about snakes. But if you search for programming first, and then python second, it will now give back programming results on the second search. This continues to apply if you searched "programming" last week.
This behavior is actually very nuanced and impressive to watch, once you understand what's going on.
I don't think google is becoming more user friendly at the expense of being technical. It certainly isn't for me. What your problem sounds like is that it's built two separate profiles for you - one of which is what you're likely to search of desktop, and the other for what you're likely to search on mobile.
I don't think the term user friendly is the right term. More like they have been targeting a different user over the years (also the content on the web has exploded).
Although most of the time Google will give me technical results if I can coax it.
Genuine question: why should this be any more difficult than searching for any other type of character? I've long found it hard to understand why Google is so bad at searching for non-alphanumeric characters.
It's the most frustrating "feature" I've ever seen. GitHub, the platform for hosting code, has a search function that doesn't work for code. How does that make any sense?!
Fixing that seems like PM101 material, yet here we are in 2017 with this still being a thing...
This will be extremely helpful next time I have to use a Haskell library that decides to implement everything as infix operators named "~<$>" and ".~=" and stuff.
But it's a sight better than it was before. It actually shows meaningful programming language results. And if I call the operator by it's Haskell name at the same time, I get very good results:
Animats|9 years ago
Google Code Search (2006-2013) [1] was more useful. I miss that. Its search allowed regular expressions.
[1] https://en.wikipedia.org/wiki/Google_Code_Search
kristianp|9 years ago
TACIXAT|9 years ago
I really believe that the technical crowd drives what becomes popular (app recommendations for family and friends). I feel a lot of the "Google hacking" queries have become less obvious and the search bubble stuff was getting bothersome. This is definitely a step in the right direction. Hopefully I'll be a little less frustrated with results in the future.
johnfn|9 years ago
This behavior is actually very nuanced and impressive to watch, once you understand what's going on.
I don't think google is becoming more user friendly at the expense of being technical. It certainly isn't for me. What your problem sounds like is that it's built two separate profiles for you - one of which is what you're likely to search of desktop, and the other for what you're likely to search on mobile.
zitterbewegung|9 years ago
Although most of the time Google will give me technical results if I can coax it.
binarymax|9 years ago
chimprich|9 years ago
tyingq|9 years ago
mxstbr|9 years ago
Fixing that seems like PM101 material, yet here we are in 2017 with this still being a thing...
kolemcrae|9 years ago
When I was a teenager I made music under the name shark^^bait
The ^^ is what made it stand out from others.
The issue is there is no efficient way to search for that phrase with the special characters.
I have no idea if I can still find the absolutely god awful music I made back then.
Using the phrase match in google just searches for sharkbait which doesn't help at all.
It doesn't help that years later a little movie called Finding Nemo came out.
rspeer|9 years ago
tomsmeding|9 years ago
lamida|9 years ago
macintux|9 years ago
james2vegas|9 years ago
it's google though shouldn't be surprised
AaronFriel|9 years ago
">>= operator": https://www.google.com/#q=%3E%3E%3D+operator&*
But it's a sight better than it was before. It actually shows meaningful programming language results. And if I call the operator by it's Haskell name at the same time, I get very good results:
">>= bind": https://www.google.com/#q=%3E%3E%3D+bind&*
Or just the language name:
">>= Haskell": https://www.google.com/#q=%3E%3E%3D+haskell&*
kyrra|9 years ago
doall|9 years ago
ino|9 years ago
hashhar|9 years ago
TheGrassyKnoll|9 years ago
<your programming problem> !so
Takes your search directly to Stack Overflow
If you don't like the results, try it again with !g and your search is submitted to Google.
They've got 9000+ bangs now:
https://duckduckgo.com/bang?q=