You can't google 9999999..99999999999999999999999
21–30 of 84 posts
Re: You can't google 9999999..99999999999999999999999
#22Re: You can't google 9999999..99999999999999999999999
#23On a faintly related note, I once was calculating partitions, using a relatively inefficient method (memoization: if f(n,k) is the number of distinct ways to express n as the unordered sum of integers no greater than k, then f(n,k) = f(n-k,k) + f(n,k-1)). My computer started to feel the strain in the thousands (this algorithm is O(n^2) in space and time). I then googled for the partition of, say, 1034, which is: 9136…
Re: You can't google 9999999..99999999999999999999999
#24The double dot indicates that this is a ranged query. 11..22 would be to search for all integers between 11 and 22. The effect is that the search is too broad. The problem is more likely to be that the range search is a mapreduce that performs a search for each item in the range. You can imagine why that's a bad idea, and some aggressive timeouts are probably what stop it from going too far. Plus the numbers in the r…
If this were true, surely it should allow you to use quotes to force it to ignore the "range" operator... http://www.google.com/search?q=%229999999..99999999999999999...
Re: You can't google 9999999..99999999999999999999999
#25On a faintly related note, I once was calculating partitions, using a relatively inefficient method (memoization: if f(n,k) is the number of distinct ways to express n as the unordered sum of integers no greater than k, then f(n,k) = f(n-k,k) + f(n,k-1)). My computer started to feel the strain in the thousands (this algorithm is O(n^2) in space and time). I then googled for the partition of, say, 1034, which is: 9136…
Re: You can't google 9999999..99999999999999999999999
#26On a faintly related note, I once was calculating partitions, using a relatively inefficient method (memoization: if f(n,k) is the number of distinct ways to express n as the unordered sum of integers no greater than k, then f(n,k) = f(n-k,k) + f(n,k-1)). My computer started to feel the strain in the thousands (this algorithm is O(n^2) in space and time). I then googled for the partition of, say, 1034, which is: 9136…
It should be pointed out here for everyone else that in general, if you want terms of a well-known integer sequence, OEIS (and the links section for longer tables like that) is a good place to check.
They are also quite capable of blowing my mind sometimes. (Try "When will the ISS be visible?" or "coastline length of africa / length of stride")
Re: You can't google 9999999..99999999999999999999999
#27Bing to the rescue: http://www.bing.com/search?q=9999999..9999999999999999999999... Pretty similar URL format eh?
Bing doesn't really come to the rescue -- the X..Y format on Google searches for numbers in a range. Bing seems to just try to find that string as plain text.
Re: You can't google 9999999..99999999999999999999999
#28Also remember how you used to be able to search for anything up to the 1000th item (10 pages of 100 results). Not anymore for a long time now. Google sucks it all in but won't share and play nice with others.
Why not allow such searches unless a bot is detected (too many pages too quickly, etc.)
Re: You can't google 9999999..99999999999999999999999
#29Earlier quoted context omitted.
If this were true, surely it should allow you to use quotes to force it to ignore the "range" operator... http://www.google.com/search?q=%229999999..99999999999999999...
It ignores the quotes a lot of the time. They are less explicit than you may imagine.