News for hackers. Stuff that matters.
Re:Introducing the new compose in Gmail by jsdalton on Tuesday October 30, 2012 @12:32PM (#4718086)
I hate being the guy who sidetracks a thread off the bat by complaining about something unrelated, but...

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.

Re:Introducing the new compose in Gmail by andrewljohnson on Tuesday October 30, 2012 @03:52PM (#4719162)
Ugh, why would anyone up-vote this comment? Some how this is the top comment, even though it doesn't address the content of the article. This happens all the time on HN and I find it very annoying.

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.

Re:Introducing the new compose in Gmail by guelo on Tuesday October 30, 2012 @04:34PM (#4719400)
I found your meta-meta comment more useless, better to just let it be. OTOH this meta-meta-meta comment is fantastic, especially this sentence.
Re:Introducing the new compose in Gmail by TeMPOraL on Tuesday October 30, 2012 @06:01PM (#4719924)
> These meta-comments may seem harmless, but when this is the top comment, it stifles the entire discussion about the article.

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).

Re:Introducing the new compose in Gmail by GHFigs on Tuesday October 30, 2012 @07:45PM (#4720359)
it doesn't address the content of the article

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?

Re:Introducing the new compose in Gmail by MaysonL on Tuesday October 30, 2012 @05:49PM (#4719861)
I never did read the article because of the same features that the comment you're complaining about complains about. The format of the google blog seriously sucks.

EDIT: I just realized: the Readability bookmarklet manages to hide all the cruft, and make the post readable. Amazing.

Re:Introducing the new compose in Gmail by afterburner on Tuesday October 30, 2012 @04:57PM (#4719568)
He's getting upvoted because it had to be said... finally.
Re:Introducing the new compose in Gmail by Kylekramer on Tuesday October 30, 2012 @06:57PM (#4720160)
Yeah! After all, it isn't like this comes up every (http://news.ycombinator.com/item?id=4070192) single (http://news.ycombinator.com/item?id=3767025) time (http://news.ycombinator.com/item?id=4196833) a official Google blogpost is submitted or even is brought up.
Re:Introducing the new compose in Gmail by te_chris on Tuesday October 30, 2012 @04:01PM (#4719212)
I'm finding HN harder and harder to deal with without comment upvote counts to provide perspective as a filtering mechanism. I find that regulars and comments like this always tend to get upvoted, even when they're normally far from the most insightful comments posted.
Re:Introducing the new compose in Gmail by ablefire on Tuesday October 30, 2012 @08:49PM (#4720567)
It would be helpful to have some way to collapse a comment thread that we are not interested in.
Re:Introducing the new compose in Gmail by tharris0101 on Tuesday October 30, 2012 @04:23PM (#4719333)
Normally I'd agree but I came in here to post this same thing as the page is almost unreadable for me in Chrome.
Re:Introducing the new compose in Gmail by jaydz on Tuesday October 30, 2012 @04:13PM (#4719271)
Agreed, these ux complaints are getting annoying.
Re:Introducing the new compose in Gmail by MaysonL on Tuesday October 30, 2012 @05:50PM (#4719866)
So, of course, are these horrible ux's.
Re:Introducing the new compose in Gmail by JoshTriplett on Tuesday October 30, 2012 @12:47PM (#4718175)
Worse yet, they've somehow broken the ability to hit space to scroll by a page.
Re:Introducing the new compose in Gmail by zaidf on Tuesday October 30, 2012 @01:04PM (#4718282)
That is keeping with google's newly found traditions. For example, the ajax-ing of search has mostly broken the back key among others.

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.

Re:Introducing the new compose in Gmail by DanBC on Tuesday October 30, 2012 @01:27PM (#4718391)
> 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.

Re:Introducing the new compose in Gmail by barrkel on Tuesday October 30, 2012 @02:22PM (#4718678)
And how many millions of correct searches was that? How many millions of extra seconds are spent wrapping whole words in quotes rather than just a '+'? It could even be costing lifetimes!

+ was changed because of Google+ branding, IMO.

Re:Introducing the new compose in Gmail by TeMPOraL on Tuesday October 30, 2012 @06:04PM (#4719934)
> Google needs to be usable by everyone.

Since when AJAX search is more usable than JavaScript-less one? I'd say it's strictly (in the mathematical sense) other way around.

Re:Introducing the new compose in Gmail by zmj on Tuesday October 30, 2012 @03:09PM (#4718951)
> Google needs to be usable by everyone.

Why does Google need to work the same way for everyone?

Re:Introducing the new compose in Gmail by majorlazer on Tuesday October 30, 2012 @01:10PM (#4718314)
I am one of those people that loves the AJAX search. I know it's generally hated around here but I think getting the suggested results as you type in your search is one of the best search features Google has implemented.

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.

Re:Introducing the new compose in Gmail by zaidf on Tuesday October 30, 2012 @01:17PM (#4718349)
You are talking about Suggestions which is an entirely different feature than auto-refreshing of search(though both use ajax so I could have used a better description in my OP). I personally love Suggests as much as you.

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.

Re:Introducing the new compose in Gmail by tripzilch on Tuesday October 30, 2012 @03:08PM (#4718945)
BTW you can fix both of these issues by disabling Javascript for http?://www.google.com/search/* (I use the "site preferences" in Opera for this, but I assume other browsers have similar built-in features). What you get back is something very much like the old vanilla Google web search.

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.

Re:Introducing the new compose in Gmail by sesqu on Tuesday October 30, 2012 @06:37PM (#4720075)
Do beware turning off JS; the results page no longer has a submit button for submitting new searches.
Re:Introducing the new compose in Gmail by hollerith on Tuesday October 30, 2012 @01:23PM (#4718378)
Google seems to be one of the prime culprits making web pages and browsers so complicated that functions useful for reading which used to work everywhere are now broken on a significant number of pages.

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.

Re:Introducing the new compose in Gmail by abecedarius on Tuesday October 30, 2012 @02:28PM (#4718713)
Besides the scrolling problem, the pinned header also pins down a low-value use for the easiest-to-read part of the page. That is, reading on a laptop you have a narrow screen set low, making you bend your neck to read the lower parts of the page, where all these jokers force the actual text you're trying to read.
Re:Introducing the new compose in Gmail by rdw on Tuesday October 30, 2012 @02:04PM (#4718574)
They also don't properly filter keyboard events, so Cmd-Left navigates to the next most recent article, rather than browser-back.
Re:Introducing the new compose in Gmail by rbanffy on Tuesday October 30, 2012 @03:47PM (#4719146)
> I hate being the guy who sidetracks a thread off the bat by complaining about something unrelated, but...

Then don't do it.

Re:Introducing the new compose in Gmail by dredmorbius on Tuesday October 30, 2012 @01:55PM (#4718529)
Fails to work w/o javascript enabled as well.

Fail Google.

Re:Introducing the new compose in Gmail by EdiX on Tuesday October 30, 2012 @05:56PM (#4719894)
Disable cookies, watch the gears spin forever. They made a web page that requires javascript and cookies to view a piece of static content.
Re:Introducing the new compose in Gmail by acqq on Tuesday October 30, 2012 @05:10PM (#4719638)
Absolute fail. This is really one of only a few sites that I know which don't present the content as HTML. Unbelievable.
Re:Introducing the new compose in Gmail by dredmorbius on Tuesday October 30, 2012 @05:32PM (#4719773)
Most of Gawker Media performs (or fails) similarly. There are others. I typically just reject them.
Re:Introducing the new compose in Gmail by masklinn on Tuesday October 30, 2012 @12:51PM (#4718202)
I find this theme great actually: it plain and simply doesn't work in Camino, which is my browser of choice, so I just blacklist any site which shows "the gear"
Re:Introducing the new compose in Gmail by zever on Tuesday October 30, 2012 @09:46PM (#4720729)
It also doesn't work on Dolphin Browser Mini for Android, which is what I use when I'm in low-reception areas. It is really frustrating to wait forever for a page to load only to find it's doing some unneeded animation that makes it completely unreadable on mobile.
Re:Introducing the new compose in Gmail by devbryce on Tuesday October 30, 2012 @01:13PM (#4718330)
You blacklist a site based on that it doesn't work on a web browser that isn't even on the list of the 10 most used browsers? (src - http://www.w3counter.com/globalstats.php)
Re:Introducing the new compose in Gmail by MatthewPhillips on Tuesday October 30, 2012 @01:26PM (#4718390)
Displaying text articles in a cross-browser way has been a solved problem for more than a decade, the parent's browser of choice isn't to blame here.
Re:Introducing the new compose in Gmail by shinratdr on Tuesday October 30, 2012 @06:01PM (#4719919)
Why not? The web browser in question is basically just FF10 with a more OS X friendly UI stapled onto it. The site owner shouldn't have to do anything special to get it working in Camino, just don't make it the most over-the-top and animation-heavy blog you can.

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.

Re:Introducing the new compose in Gmail by hnriot on Tuesday October 30, 2012 @01:29PM (#4718395)
Seriously? Chrome, Firefox, Safari... etc... Time to upgrade and stop blaming the web for advancing.
Re:Introducing the new compose in Gmail by 001sky on Tuesday October 30, 2012 @02:31PM (#4718727)
Advancing? Most 'scripting is taking a pound of flesh from the user experience, in return for little to no actual gain.
Re:Introducing the new compose in Gmail by hnriot on Tuesday October 30, 2012 @02:34PM (#4718747)
scripting? I have no idea what you're referring to, but using a browser capable of rendering the web properly is a requirement these days. That's why they have mostly gone to an automatic update model, the web is fluid and changes rapidly, to keep up you need to be running a modern browser.
Re:Introducing the new compose in Gmail by shinratdr on Tuesday October 30, 2012 @06:02PM (#4719927)
> That's why they have mostly gone

Actually that's incorrect. The majority of browsers don't utilize a rapid release system. Really, only Firefox and Chrome do.

Re:Introducing the new compose in Gmail by hnriot on Wednesday October 31, 2012 @10:58AM (#4723086)
Firefox and chrome are "most browsers"
Re:Introducing the new compose in Gmail by masklinn on Wednesday October 31, 2012 @01:21PM (#4723990)
No, they are most used browsers, but they are not "most browsers" as they are 2 out of 5 "standard" major browsers (IE, Opera, Firefox, Safari, Chrome)
Re:Introducing the new compose in Gmail by tedunangst on Tuesday October 30, 2012 @04:36PM (#4719414)
massklin is not complaining he can't use an old browser to navigate a 3D maze of blog posts jurassicpark style.
Re:Introducing the new compose in Gmail by masklinn on Wednesday October 31, 2012 @02:01AM (#4721445)
I don't blame the web for advancing, when I see a reason for sites not to work I use an alternative browser. We're talking about a fucking blog here, not advanced data visualisation, if you just have to shit over the very core of the web for a blog, I can't bring myself to care about what you have to say: it won't matter that much anyway.
Re:Introducing the new compose in Gmail by iigs on Tuesday October 30, 2012 @02:59PM (#4718882)
Laughably bogus (almost entirely unreadable) on a former flagship Android phone that is just barely out of contract, too.
Re:Introducing the new compose in Gmail by jmsduran on Tuesday October 30, 2012 @02:49PM (#4718831)
I must admit, I am not a fan of the default blogspot theme. I miss their old blog theme that worked fast and well with or without JavaScript enabled.
Re:Introducing the new compose in Gmail by Nux on Wednesday October 31, 2012 @05:44AM (#4721985)
+1000! I've been more and more bothered by that shit "gears" theme, too. High CPU usage, cannot be viewed without javascript capable/enabled etc. Sometimes I get the feeling the google devs are being replaced by retarded monkeys.
Re:Introducing the new compose in Gmail by jrockway on Tuesday October 30, 2012 @12:37PM (#4718115)
Apparently Blogger customers want this sort of design, so Google tests the themes on their own blogs before giving them to normal users. More feedback, etc.
Re:Introducing the new compose in Gmail by tharris0101 on Tuesday October 30, 2012 @04:22PM (#4719329)
I was about to come on here and post this same thing.

The worst part is the font. Almost unreadable using Chrome/Win7 (Their own browser!).

Re:Introducing the new compose in Gmail by acqq on Tuesday October 30, 2012 @06:32PM (#4720048)
Anybody who tries to defend them should just imagine how the web would look like when every page on the web would present you a more seconds of gears before the content, or absolutely nothing without the JavaScript.
Re:Introducing the new compose in Gmail by uladzislau on Tuesday October 30, 2012 @06:42PM (#4720100)
If somebody's from Google is reading it, please fix your blog theme! It's the most unusable theme, period.
Re:Introducing the new compose in Gmail by iamrohitbanga on Tuesday October 30, 2012 @12:35PM (#4718098)
They have a sort of theme roller implemented. Watch the dropdown on top left.