It's not just that I don't want to scroll past this comment. These meta-comments may seem harmless, but when this is the top comment, it stifles the entire discussion about the article. Instead of people discussing the merits of the new GMail UI, there is an endless chain of replies burying all the topical comments.
I've said it before - I'd like to see a community guideline advising people not to make comments like this. These comments end up being easy ways to score points, entertaining for the people involved in the criticism, but harmful for the topical discussion. If it's a "Show HN" post about a hacker's new project, it seems topical to criticize the technology, but when it's a blog post, it seems so lame to criticize the blog software.
This kind of complaint belongs in its own thread - it should be a blogpost or something. The comment doesn't even apply to me - the page works perfectly and crisply for me.
And for others this is one of the main values of HN. Usually the discussions here are much better / insightful than original articles, and quite often those interesting discussions are tangential to the article itself. Let the community decide what to discuss about, in terms of topic (and the community do decide, by the means of an upvote).
I wholeheartedly disagree. The singing and dancing crap that people surround their text and images with is content. It's just crap content. Think about it the other way: if it's not content, why is it even there? Why does a blog need a loading screen?
EDIT: I just realized: the Readability bookmarklet manages to hide all the cruft, and make the post readable. Amazing.
Shit Case 1: sometimes you do a search, find a new phrase and begin typing it only to see the phrase disappear from the original search results and replaced with updated results for an incomplete and often incoherent query.
Shit Case 2: often I begin typing a new search query and realize mid "sentence" that the current query was fine. Well, too late. Because the results have already refreshed. Hitting the back key does little good. In best case, it doesn't work. In worst case, it will take you to the previous physical page that you were on before you came to google.
I find some of these changes mind boggling and can only convince myself to accept them by tell myself "hey google looks at the numbers, may be most folks just like it". Particularly the ajax search...annoys the crap out of me and finds way to enable itself even when I disable it.
Google needs to be usable by everyone. They iterate the product to make sure that most people get good search results. But this means that some people are getting sub-optimal results, especially as Google makes changes to the way search works.
Google didn't used to use stemming. Some words are now stemmed automatically. Google didn't used to substitute words. Some words are now substituted automatically. Google used to use + to force inclusion of a word, but they've dropped that and now use quotes to "force" "inclusion" of words "or phrases".
People reading HN might think that + is easy enough to use, and "enclosing" "every" "word" in "quotes" is stupid, but Google does have the numbers. (http://insidesearch.blogspot.co.uk/2011/11/search-using-your...)
> In the past, we provided users with the “+” operator to help you search for specific terms. However, we found that users typed the “+” operator in less than half a percent of all searches, and two thirds of the time, it was used incorrectly.
Check my math, but I think that means that + was used correctly in only 1 out of 600 searches.
+ was changed because of Google+ branding, IMO.
Since when AJAX search is more usable than JavaScript-less one? I'd say it's strictly (in the mathematical sense) other way around.
Why does Google need to work the same way for everyone?
For example, let's say I found some new framework for a new language I haven't worked with. I can easily find competing frameworks by typing in something like '[framework name] vs' and Google will will suggest the most commonly compared frameworks. I think it's very useful when you don't know exactly what you are searching for. Yes, I know it has some usability issues but in my opinion the pros outweigh the cons.
What I hate is when I type, say a few letters of my query, and begin seeing frivolous search results begin to appear. I hate when I hit the back key, often it takes me to the previous page or simply removes the last letter from my query and updates the results. I hate when I begin typing an obscure name I just found from another query and see it disappear after I have typed a couple of letters.
I was just fine hitting the "return" key to pull up search results.
I used to have it for quite some time, new laptop set it back to normal, and for now it hasn't quite annoyed me enough yet to set it again (also because I'm using DuckDuckGo much more these days, for similar reasons), but it was good when I had it.
I really wish Google had some setting to turn off this "instant search update" thing, as well as how the input box continuously steals the focus (this breaks many keyboard shortcuts in Opera), because the other interactive/dynamic features they do with JS on the web search page are quite useful.
Parent mentions scrolling with the space key. Another: selecting text (prior to copying it). Another: making text bigger, e.g., with the Zoom In ("+") button. Another: going to the start or end of the page. Another: scrolling without annoying or time-wasting latency.
Then don't do it.
Fail Google.
Google chose to ignore that, and they're rightfully catching flak for it. This isn't some fancy homepage, it's an informational blog. Text on a white background is the reason 100% of visitors visit. Hamming it up at the expense of non-mainstream browser users is pointless.
Actually that's incorrect. The majority of browsers don't utilize a rapid release system. Really, only Firefox and Chrome do.
The worst part is the font. Almost unreadable using Chrome/Win7 (Their own browser!).
Whatever blogspot theme Google uses for this blog is just god awful (oh, I see, this is it: http://gmailblog.blogspot.co.uk/p/as-you-may-have-noticed-gm...), and I swear it gets worse every time I view a post there.
To wit:
When I load the page I see the orange "loading" gears. Then that sliiiiides up to reveal the content. Really? Can they really not innovate here? This is a company that spends massive amounts of resources to get their homepage to load as quickly as possible. Heck, they even penalize companies in their index with slow loading times. And yet they purposefully add loading animations and transitions which add at least a second to page load, and probably more as far as time it takes me to engage in the content.
Also, every time I reload the page I see something different. Sometimes there is text in the black menu bar. Sometimes there is not. Sometimes there is an "extra" screen that slides up after the orange loading gears, sometimes not. Sometimes the sidebar navigation is there, sometimes not. Try refresh a few times yourself and you'll see.
Also, I love the five-second delay for the document URL update when you navigate via the sidebar.
All of these fancy, look-we're-using-ajax, gee-whiz-its-a-single-page-app features -- just for a simple blog post. Talk about complicating a simple problem!
Again, apologies for the rant but I couldn't even concentrate on what the blog post was saying because I was so distracted by this garbage.