Live data from Hacker News

Chief Architect of Google+ requests clarification on Google Reader

plus.google.com

21–30 of 131 posts

Re: Chief Architect of Google+ requests clarification on Google Reader

#21
post #14
post #5

Interesting, but doesn't speak too well of Google. Shouldn't Google know how people were using Google Reader before deciding to axe it? And even if that information's in a different part of the company, shouldn't the chief architect of Google+ have access to it?

Well regardless of what data google has about Reader's use... the best way to really understand how people used it is to ask.

The asking should come before the axeing.

Re: Chief Architect of Google+ requests clarification on Google Reader

#22
post #14
post #5

Interesting, but doesn't speak too well of Google. Shouldn't Google know how people were using Google Reader before deciding to axe it? And even if that information's in a different part of the company, shouldn't the chief architect of Google+ have access to it?

Well regardless of what data google has about Reader's use... the best way to really understand how people used it is to ask.

[deleted]

Re: Chief Architect of Google+ requests clarification on Google Reader

#23

G+ can't be google reader for two reasons: 1. Information density. Magazine style / tiles / graphics etc aren't the same as single line expandable headline with maybe 40 headlines visible per screen height. 2. Just the content. Reader didn't try to guess what you wanted to read or notify you what your friends were up to.

The guessing and notifying that youtube keeps wanting to push is so annoying. At some point they have to learn that what are friends like has no relevance on what we like.

Re: Chief Architect of Google+ requests clarification on Google Reader

#24

Yeah, I really don't understand what he's looking for here. He wants constructive criticism about what parts of Google Reader were useful, but if you complain at all, your comment will be deleted. Google Reader itself was the useful piece. It aggregates RSS feeds. I don't really know how else you can explain that "yes, it aggregated RSS feeds, and I like to read all of my RSS feeds in one place".

i also think this line of thinking is silly. the Googler is assuming a set of features is what made Google Reader the best RSS reader on the market. while that is true in essence (features do add up to the overall product) i don't think any 1 feature in reader was killer. rather, the collection of all the features made the app itself killer.

Re: Chief Architect of Google+ requests clarification on Google Reader

#25
post #7

Earlier quoted context omitted.

He's asking for specific elements of the reader that people found useful, enjoyable, easy to use. I'd say that's valuable. How is it not?

So like, the "Subscribe" button, and the list view? That's what was useful. I really don't get what he's aiming for here... obscure features that may have existed that only some people thought were useful?

[deleted]

Re: Chief Architect of Google+ requests clarification on Google Reader

#26
post #7

Do the benefits of an RSS reader really need explanation? Or is he simply hoping to hear some unexpected input from this?

He's asking for specific elements of the reader that people found useful, enjoyable, easy to use. I'd say that's valuable. How is it not?

Why doesn't he just ask the google reader staff?

Re: Chief Architect of Google+ requests clarification on Google Reader

#27

"Comments which disregard the previous paragraph will simply be deleted. Comments complaining about my deleting those comments will result in me blocking and/or mercilessly mocking you for failing to read instructions. Comments complaining about that will lead to some interesting replies in a combination of languages, probably starting with Yiddish and moving on from there. " I just love this offensive/defensive writ…

So you're saying he's selecting for answers from people with weak egos?

Re: Chief Architect of Google+ requests clarification on Google Reader

#28

G+ can't be google reader for two reasons: 1. Information density. Magazine style / tiles / graphics etc aren't the same as single line expandable headline with maybe 40 headlines visible per screen height. 2. Just the content. Reader didn't try to guess what you wanted to read or notify you what your friends were up to.

Yes. If Google wants to satisfy Reader users, they have to push back against G+ taking over everything. G+ is supposed to br about a seamless integration between products. Making all the features subservient to the Stream is putting style --no, fashion-- over substance.

That is the philosophy of G+, though-- to cannibalize Google into a Facebook clone. G+ is like the evil vizier whispering in the senile monarch's ear.

Re: Chief Architect of Google+ requests clarification on Google Reader

#29

G+ can't be google reader for two reasons: 1. Information density. Magazine style / tiles / graphics etc aren't the same as single line expandable headline with maybe 40 headlines visible per screen height. 2. Just the content. Reader didn't try to guess what you wanted to read or notify you what your friends were up to.

..and you know what? I like text.

I 'circled' a bunch of people from the numerous Hacker News communities on G+, and I see far too many pictures and videos in the feed. And mostly personal life stuff, like their pets, or lunch, or some trees or whatever. (This is also my current complaint with App.net, but that's a different story).

I really wish there were a way to filter by post type (text and links only) in Google+, to bring it even one small step closer to replacing Reader.

Re: Chief Architect of Google+ requests clarification on Google Reader

#30
post #24

Yeah, I really don't understand what he's looking for here. He wants constructive criticism about what parts of Google Reader were useful, but if you complain at all, your comment will be deleted. Google Reader itself was the useful piece. It aggregates RSS feeds. I don't really know how else you can explain that "yes, it aggregated RSS feeds, and I like to read all of my RSS feeds in one place".

i also think this line of thinking is silly. the Googler is assuming a set of features is what made Google Reader the best RSS reader on the market. while that is true in essence (features do add up to the overall product) i don't think any 1 feature in reader was killer. rather, the collection of all the features made the app itself killer.

In Mountain View, all problems are engineering problems.

Even when they aren't.

Post reply on HN