Live data from Hacker News

Introducing the new compose in Gmail

gmailblog.blogspot.co.uk

151–160 of 202 posts

Re: Introducing the new compose in Gmail

#151
post #132

Earlier quoted context omitted.

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 mer…

Agreed, these ux complaints are getting annoying.

So, of course, are these horrible ux's.

Re: Introducing the new compose in Gmail

#153

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…

Fails to work w/o javascript enabled as well. Fail Google.

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

#154

Earlier quoted context omitted.

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"

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 )

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

#155

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…

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 mer…

> 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

#156
post #102
post #100

Earlier quoted context omitted.

Advancing? Most 'scripting is taking a pound of flesh from the user experience, in return for little to no actual gain.

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.

> 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

#157
post #67
post #44

Earlier quoted context omitted.

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 real…

> 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 tha…

> 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

#158
Does anyone else suffer from EXTREMELY slow gmail. This happens for me across all devices, browsers, and even IMAP. 30+ seconds to load messages sometimes and lots of 17, 317 and 503 errors.

I've tried every recommendation, and of course hear nothing back from their support or in their forums. Gmail is almost unusable for me now.

Any recommendations or contacts would be appreciated. It seems the only way to get help from Google is to know someone.

Re: Introducing the new compose in Gmail

#159

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…

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

#160
post #44

Earlier quoted context omitted.

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 real…

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…

Do beware turning off JS; the results page no longer has a submit button for submitting new searches.
Post reply on HN