Live data from Hacker News

Google's Inevitable Ruin Begins

pcmag.com

21–30 of 72 posts

Re: Google's Inevitable Ruin Begins

#21
Dvorak could legitimately be described as a professional troll.

"you get over 20 pages of large thumbnails all on the same huge page....And because thousands of useless large thumbnails are loaded, a huge waste of user bandwidth takes place each time."

Beware commenting on things you don't understand, because often it just makes you look like a fool.

In this case, Dvorak apparently didn't notice that while all of the images "were on" the same page, they were simply placeholders until you scroll.

If an image exists outside of the viewport, does it exist? Not necessarily.

As to them being large images....welcome to the high speed world, John. We've graduated beyond dial-up.

"So instead of being able to scan the entire page with a simple glance to find an image from say, usgs.gov, you have to put the cursor on each and every image and wait for a pop out with the information."

Who searches for images by domain like that? Few users of Google image search, I suspect, with the average user casually looking for some images to "borrow" for their book report or blog. The source domain just doesn't really matter to most users, again speculating (though presumably Google has actually verified this).

But say you really want to see images from usgs.gov? site:usgs.gov, e.g. http://images.google.com/images?hl=en&q=site%3Ausgs.gov+...;

And of course you can search by size (larger than, or a specific absolute size), and so on.

There will always (always) be people who complain about change. John, in this case, is just plying his trollish trade, however.

Re: Google's Inevitable Ruin Begins

#22
Personally I love the new google images. However I would quickly point out that some of the reasons people have left google is their frustration with the magnitude google relies on "the numbers" I highly doubt that the changes are hurting them, becuase if they were... they wouldn't keep it.

Re: Google's Inevitable Ruin Begins

#23
I'm not going to actually go check, but I'm pretty sure the images still load one page at a time, when you scroll to the bottom of the last page (or farther). How can you have a job at PCMag and not acknowledge or even be aware of this?

Re: Google's Inevitable Ruin Begins

#24
post #8

John Dvorak seems to have an unlimited supply of complaints, and rarely anything constructive to say. Wikipedia suggests he's never built anything of his own. Always a bridesmaid, never a bride. Perhaps that's part of it?

It's possible to be a good tech journalist without having coded something yourself (though that's not to say that Dvorak is a good journalist). Sure, it would probably be an asset, and a lack of technical context can make people write some stupid stuff, but not having built something does not automatically invalidate anyone's opinions.

Most journalists have never worked in their fields, but nobody's complaining about that. The asinine idea that nobody's allowed to have an opinion about any tech company without being a programmer is getting old fast.

Re: Google's Inevitable Ruin Begins

#25
I disagree with the author, and think that he hasn't used google image search very extensively.

"Instead of the single page of thumbnails, you get over 20 pages of large thumbnails all on the same huge page."

The (near) endless scrolling model works better for rapidly sorting large sets of images, not worse.

"There is no information, just endless thumbnails. No sizes, no locations to scan, nothing! ... Now you have to place the pointer on top of each image for ... size and location information."

If you are optimizing for a an interface for sorting the most images possible, removing text makes sense to me. Also, sorting options for the image size is now on the left, which I find more useful than reading text below each image.

The pop-ups also contain controls which the author ignores that are very handy: similar images, and different sizes of the same image.

Re: Google's Inevitable Ruin Begins

#27
Technology people may not like Google's recent work (me included), but two things must be kept in mind:

1. techies are the minority

2. Google is said to split test heavily, maybe even pathologically

So if a new feature stays it's probably because non-technical people liked it and Google is probably doing the right thing from a business perspective.

Re: Google's Inevitable Ruin Begins

#28
post #26

Putting 'Dvorak' in the title would have saved me some time.

I'd upvote you twice if I could. I actually audibly groaned when I saw who the author was. Didn't even read the article, I knew it was going to be full of crap. I can't believe I graced him with a pageview. Ugh.

Re: Google's Inevitable Ruin Begins

#29
post #8

John Dvorak seems to have an unlimited supply of complaints, and rarely anything constructive to say. Wikipedia suggests he's never built anything of his own. Always a bridesmaid, never a bride. Perhaps that's part of it?

It's possible to be a good tech journalist without having coded something yourself (though that's not to say that Dvorak is a good journalist). Sure, it would probably be an asset, and a lack of technical context can make people write some stupid stuff, but not having built something does not automatically invalidate anyone's opinions. Most journalists have never worked in their fields, but nobody's complaining about…

Absolutely, and I didn't mean to imply otherwise. But Dvorak seems particularly quick to call tech companies stupid, and I wonder if that's a result of not having been in the trenches himself.

Re: Google's Inevitable Ruin Begins

#30
post #21

Dvorak could legitimately be described as a professional troll. "you get over 20 pages of large thumbnails all on the same huge page....And because thousands of useless large thumbnails are loaded, a huge waste of user bandwidth takes place each time." Beware commenting on things you don't understand, because often it just makes you look like a fool. In this case, Dvorak apparently didn't notice that while all of the…

Beware splitting hairs when you are ignoring the main point. The new google image search is worse than the old one imo so dvorak's point stands even if he got a few technical details wrong.

I also agree with him that it's a bad sign when a company seems to be doing things just because their competitors did something similar.

Post reply on HN