Hacker News new | past | comments | ask | show | jobs | submit login

Can you explain what you don't like about it? I was just thinking the (almost) opposite, that a full page reload after searching seems unnecessary.



Google Instant is irritating because I'm trying to type a search string into a field in the middle of the page, and as soon as I enter a single keystroke, my entire thought process is interrupted when the field I'm focusing on is thrown upwards to the top of the page, without waiting for me to confirm that I'm finished typing.

So I want to search for "apple" and guess what:

I type the letter "a"...

Now the whole page is disrupted, and I have to stop, and check the page, to make sure the sudden change is what I expected it to be. Is the page doing what I intended? I only typed one letter...

Did I actually type the letter "a", or did my finger slip and type the letter "s"? Wait, where's the field? Oh, it's up at the top of the page now... What was I doing? Oh, right, I was going to search for "apple"...

Why did the page change, when I wanted it to stay put, while I complete my thought? Why didn't the page wait until I pressed the enter key, to confirm that I was finished, and ready to search for the intended query?

Do I care about whether the page sends an ordinary post with a form submission, and reloads the page? No.

Do I care about whether the page sends an AJAX request, and is re-rendered by a JavaScript library? No.

I want the page to remain static and reliable while I perform my task. After I'm done typing, it can go crazy, and do whatever.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: