Earlier quoted context omitted.
Then they'll build one now.
It's almost too late to do that. Products that were slowly grinding are now seeing much more traction, and the initial exodus has passed. There may be a second one when it is officially stopped, but it would be difficult to compete with those products that grabbed customers already.
Sorry Google; you can Keep it to yourself
31–40 of 242 posts
Re: Sorry Google; you can Keep it to yourself
#32Google Reader had an easy and clear migration path to export your data. I can't understand why people keep bashing Google for it. Just take your data to somewhere else. If tomorrow Keep goes away they'll do the same.
Basically, Google is canceling the direct RSS blog subscriptions that countless blog readers have accumulated over the years. To be sure, it's a fairly low barrier for them to export and thus renew through another provider (be it Twitter or another RSS reader or Google Plus). But even though this seems to readers of Hacker News like a fairly low barrier, some casual or less tech-savvy readers will be left behind.
At least that's what I expect to happen to my blog, which is followed by a very non-technical audience -- the bulk of whom subscribe through some Google Reader-powered source.
Re: Sorry Google; you can Keep it to yourself
#33Google Reader had an easy and clear migration path to export your data. I can't understand why people keep bashing Google for it. Just take your data to somewhere else. If tomorrow Keep goes away they'll do the same.
Is the closing of Reader ideal? NO! But you have to know something like that might happen, plus they're giving enough time for people to migrate to other services and exporting your data couldn't be easier.
My question is what are you going to do? Go to other services for everything, never use a google product again in case it closes down? I'd argue that there is even a better chance of any other small dedicated startup to fall apart than google closing down their one of their product, if you wan't to be really sure something is "forever", self host, but don't lie to yourself, that's not even close to a perfect solution.
Re: Sorry Google; you can Keep it to yourself
#34Google Reader had an easy and clear migration path to export your data. I can't understand why people keep bashing Google for it. Just take your data to somewhere else. If tomorrow Keep goes away they'll do the same.
Re: Sorry Google; you can Keep it to yourself
#35Re: Sorry Google; you can Keep it to yourself
#36Re: Sorry Google; you can Keep it to yourself
#37Google Reader had an easy and clear migration path to export your data. I can't understand why people keep bashing Google for it. Just take your data to somewhere else. If tomorrow Keep goes away they'll do the same.
And as Malik has raised the question in his post - what's in it for Google? No one seems to know this. They might just be testing one of their APIs by building this app.
Anyway, this app is clunky.
[1]Google Reader used to mean RSS the way Search means Google Search and this is very important.
Re: Sorry Google; you can Keep it to yourself
#38Is this also a warning to Evernote to never remove features? I'd hate to be a company that makes products that Om uses.
I don't know any company who would remove features that millions of people use every single day.
Re: Sorry Google; you can Keep it to yourself
#39But listen to me when I tell you how to run your service that costs money.
Riiiiigghhhttt.
Re: Sorry Google; you can Keep it to yourself
#40Google Reader had an easy and clear migration path to export your data. I can't understand why people keep bashing Google for it. Just take your data to somewhere else. If tomorrow Keep goes away they'll do the same.
You realise there were feed services that went kaput because of Reader[1] and one fine day Google decided to give it an injection. Is it really that difficult to see this happening to sth like Evernote or Simplenote? I mean seeing Google's reach it's very much possible. And as Malik has raised the question in his post - what's in it for Google? No one seems to know this. They might just be testing one of their APIs b…
People keep saying something like this without providing real examples. I can believe Reader's existence might have depressed the market for new feed readers (though there have long been competitors around--lots of open source and built in ones, and a few for-pay ones too, like Feedly), but I haven't been able to personally think of any feed readers that were crushed by Reader coming out.
I may just have forgotten them, though (2005 was a long time ago). Anyone have good examples?