While the new crop of "Instance [website] Search" projects are cool, I feel like most are missing the key feature of Google Instant: predictions. Without predictions, the user never knows what search returned the current results. Instead of instant search, these examples feel like instant filtering.
Rather than wiping the results and re-inserting the new ones after each character is added it would look better if individual results were pulled out and inserted in the correct location. Some times the results don't change between key presses yet there is still a momentary flash where they're removed and re-added.<p>It would also be nice if it degraded gracefully for non-js browsers. Like Google search does.
This is the best one yet - I can actually see myself using this. It's hard to know what terms people have used on HN when searching for something. The Ask HN archives are a brilliant resource.
Nice.
But, check that some results are repeated. For example, when searching for "android ", <a href="http://news.ycombinator.com/item?id=1506909" rel="nofollow">http://news.ycombinator.com/item?id=1506909</a> and <a href="http://news.ycombinator.com/item?id=1332153" rel="nofollow">http://news.ycombinator.com/item?id=1332153</a> are listed twice.
I don't like how the results are refreshed ... it should load the results in a hidden div or something, then swap, and it should put a delta between refreshes ... I would have a second elapsed between 2 result sets displayed.<p>The indexer doesn't do a very good job, e.g. I searched for "mono" and only 4 results have been shown. Here's the Google index: <a href="http://www.google.ro/search?q=mono+site:news.ycombinator.com" rel="nofollow">http://www.google.ro/search?q=mono+site:news.ycombinator.com</a><p>Also, the address bar should be refreshed with the query searched because the URI has to be a permalink.<p>Otherwise, it's awesome.
Hey guys, author here, thanks all for the kind words. It's nice to see it reaching the front page of HN when someone with decent karma submits it.<p>Just to let you all know I've only spent about 6 hours on this and plan to polish it up somewhat as it's still quite rough. I've also got a bunch of other developers requesting inclusion into the site swell, which I'll also add.<p>Things on the todo list are visual polish, adding other services, new menu, adding the suggest feature, perhaps changing from just using the google search to better apis etc.<p>Thanks for the feedback.
Next step, grab a corpus of HN posts and do some text crunching to generate suggestions.<p>(or you could 'borrow' Feross' code, which is not condoned by Google - posts on the Interwebs say Google Suggest's "API" is not for public use - and not specific to this domain.)
Hi. I took two scripts and combined wich give fill-in words and to get direct results (still just 5) on the page with google instant. What do you guys think of the results?
url = www.googled.eu
<a href="http://bit.ly/ddUj1E" rel="nofollow">http://bit.ly/ddUj1E</a> <-- if anyone finds analytics interesting, HN moved WAY more traffic than TC. A good section of the directs are HN too.
My hat is off to you. It works in Opera and now I can get a glimpse of what Google Instant -- and other Instants that don't play nice with Opera -- is like. Thanks.
Cute idea, but it doesn't have predictions and the results are quite bad. Typing in "NoSQL" doesn't come up with the recent Heroku blog post about NoSQL.
A new meme? Surprised that it took Google to do it before it got applied to several other sites.<p>Seems that Google is still pretty darn innovative and forward-thinking.
you should adjust it so searching for "lisp" does not end up with a chunk of code w/ multiple li tags in it as being more relevant than articles that actually have the word "lisp" in them. I noticed this with a few other phrases too such as "vegan" - there are multiple "vega" chip comments that take precedence over the fully matched word.